A typical Apigee hybrid installation is made of multiple pods, as listed in the
following table.
Each of these pods require specific access to ports, and not every pod needs to communicate
with every other pod. For a detailed map of these internal connections and the security
protocols they employ, seeInternal connections.
Pod
Description
apigee-logger
Contains an Apigee logger agent that sends application logs to Stackdriver.
apigee-metrics
Contains an Apigee metrics agent that sends application logs to Stackdriver.
apigee-cassandra
Contains the hybrid runtime persistance layer.
apigee-synchronizer
Synchronizes configuration between the management (control) plane and runtime
(data) plane.
apigee-udca
Allows transfer of analytics data to the management plane.
apigee-mart
Contains the Apigee administrative API endpoint.
apigee-runtime
Contains the gateway for API request processing and policy execution.
Google recommends that you follow these methods and best practices to harden,
secure, and isolate the runtime
pods:
Method
Description
Kubernetes security overview
Review the Google Kubernetes Engine (GKE) documentSecurity overview. This document provides an overview of each layer of your Kubernetes
infrastructure, and explains how you can configure its security features to best
suit your needs.
Use network policies to restrict communication between Pods and to pods that have access
outside the Kubernetes network. For more information, seeCreating a cluster network policyin the GKE documentation.
A network policy is a specification of how groups of pods are
allowed to communicate with each other and other network endpoints.
The KubernetesNetworkPolicyresource uses labels to select pods and define
rules which specify what traffic is allowed to the selected pods.
You can implement a Container Network Interface (CNI) plugin to add network policies to
an Apigee hybrid runtime installation. Network policies let you isolate pods from outside
access and enable access to specific pods. You can use an open source CNI plugin, such asCalicoto get started.
GKE Sandbox
Enable GKE Sandbox for the Kubernetes clusters that run Apigee
hybrid. SeeGKE Sandboxfor details.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-08 UTC."],[[["\u003cp\u003eThis Apigee hybrid documentation version 1.2 is end-of-life and users should upgrade to a newer version.\u003c/p\u003e\n"],["\u003cp\u003eAn Apigee hybrid installation consists of multiple pods, each with specific port access requirements and internal connections.\u003c/p\u003e\n"],["\u003cp\u003eGoogle recommends employing methods like Kubernetes security overview, network policies, and GKE Sandbox to enhance the security and isolation of runtime pods.\u003c/p\u003e\n"],["\u003cp\u003eNetwork policies can be used to restrict pod communication and are implemented via Container Network Interface (CNI) plugins like Calico.\u003c/p\u003e\n"],["\u003cp\u003eGKE Sandbox is the Google version of gVisor, providing a virtualized container environment.\u003c/p\u003e\n"]]],[],null,["| You are currently viewing version 1.2 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\nA typical Apigee hybrid installation is made of multiple pods, as listed in the following table. Each of these pods require specific access to ports, and not every pod needs to communicate with every other pod. For a detailed map of these internal connections and the security protocols they employ, see [Internal connections](/apigee/docs/hybrid/v1.2/ports#internal).\n\n\u003cbr /\u003e\n\n| Pod | Description |\n|-----------------------|---------------------------------------------------------------------------------------------|\n| `apigee-logger` | Contains an Apigee logger agent that sends application logs to Stackdriver. |\n| `apigee-metrics` | Contains an Apigee metrics agent that sends application logs to Stackdriver. |\n| `apigee-cassandra` | Contains the hybrid runtime persistance layer. |\n| `apigee-synchronizer` | Synchronizes configuration between the management (control) plane and runtime (data) plane. |\n| `apigee-udca` | Allows transfer of analytics data to the management plane. |\n| `apigee-mart` | Contains the Apigee administrative API endpoint. |\n| `apigee-runtime` | Contains the gateway for API request processing and policy execution. |\n\n\nGoogle recommends that you follow these methods and best practices to harden,\nsecure, and isolate the runtime\npods:\n\n| Method | Description |\n|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Kubernetes security overview | Review the Google Kubernetes Engine (GKE) document [Security overview](https://cloud.google.com/kubernetes-engine/docs/concepts/security-overview). This document provides an overview of each layer of your Kubernetes infrastructure, and explains how you can configure its security features to best suit your needs. For Google Cloud Engine's current guidance for hardening your GKE cluster, see [Hardening your cluster's security](https://cloud.google.com/kubernetes-engine/docs/how-to/hardening-your-cluster). |\n| Network policies | Use network policies to restrict communication between Pods and to pods that have access outside the Kubernetes network. For more information, see [Creating a cluster network policy](https://cloud.google.com/kubernetes-engine/docs/how-to/network-policy) in the GKE documentation. A network policy is a specification of how groups of pods are allowed to communicate with each other and other network endpoints. The Kubernetes [NetworkPolicy](https://kubernetes.io/docs/concepts/services-networking/network-policies/#the-networkpolicy-resource) resource uses labels to select pods and define rules which specify what traffic is allowed to the selected pods. You can implement a Container Network Interface (CNI) plugin to add network policies to an Apigee hybrid runtime installation. Network policies let you isolate pods from outside access and enable access to specific pods. You can use an open source CNI plugin, such as [Calico](https://docs.projectcalico.org/v3.5/introduction/) to get started. |\n| GKE Sandbox | Enable GKE Sandbox for the Kubernetes clusters that run Apigee hybrid. See [GKE Sandbox](https://cloud.google.com/kubernetes-engine/sandbox/) for details. | NOTE: GKE Sandbox is the Google version of the open source project [gVisor](https://gvisor.dev/), a sandbox runtime that provides a virtualized container environment. |"]]
