Apigee deployment services

You are currently viewing version 1.13 of the Apigee hybrid documentation.This version is end of life. You should upgrade to a newer version. For more information, seeSupported versions.

ApigeeDeployment (AD) is a CustomResourceDefinition (CRD) used to define, update, and release stateless Apigee hybrid components in a Kubernetes cluster. For example, AD is used to deploy message processors to the cluster, and the release of these components are triggered by updating the version in the AD.

Before AD, certain hybrid resources were maintained manually and individually. However, with AD all these resources are maintained as an atomic deployment unit.

When you list the Apigee hybrid pods in your Kubernetes cluster, you will see these pods listed. These pods do the work to deploy and maintain the AD and validate deployment configurations.

Pod nameDescription
apigee-operatorsCreates and updates low level Kubernetes and Istio resources that are required to deploy and maintain the AD. For example, the controller carries out the release of message processors. Also validates the ApigeeDeployment configuration before persisting it in Kubernetes cluster.

To get a list of the ApigeeDeployments in your cluster, execute this command:

kubectl get ad -nnamespaceNAME                                              AGEapigee-mart-my_org                                4hapigee-runtime-my_org-my_env                      4hapigee-synchronizer-my_org-my_env                 4hapigee-udca-my_org-my_env                         4h

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-18 UTC.