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 name
Description
apigee-operators
Creates 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 -n namespace
NAME AGE
apigee-mart-my_org 4h
apigee-runtime-my_org-my_env 4h
apigee-synchronizer-my_org-my_env 4h
apigee-udca-my_org-my_env 4h
[[["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-08-29 UTC."],[[["\u003cp\u003e\u003ccode\u003eApigeeDeployment\u003c/code\u003e (AD) is a CustomResourceDefinition (CRD) used to manage the deployment, updates, and release of stateless Apigee hybrid components within a Kubernetes cluster.\u003c/p\u003e\n"],["\u003cp\u003eThe use of AD allows for the management of multiple hybrid resources as a single, atomic deployment unit, replacing previous manual management.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eapigee-operators\u003c/code\u003e pod within the cluster manages the creation and updates of low-level Kubernetes and Istio resources necessary for the deployment and maintenance of AD.\u003c/p\u003e\n"],["\u003cp\u003eYou can list the ApigeeDeployments within your cluster by using the command \u003ccode\u003ekubectl get ad -n namespace\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# Apigee deployment services\n\n| You are currently viewing version 1.14 of the Apigee hybrid documentation. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\n\n*ApigeeDeployment* (AD) is a [CustomResourceDefinition](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/#customresourcedefinitions) (CRD) used to define, update, and release stateless\nApigee hybrid components in a Kubernetes cluster.\nFor example, AD is used to deploy\nmessage processors to the cluster, and the release of these components are triggered\nby updating the version in the AD.\n\n\nBefore AD, certain hybrid resources were maintained manually and individually. However, with AD\nall these resources are maintained as an atomic deployment unit.\n\n\nWhen you list the Apigee hybrid pods in your Kubernetes cluster, you will see these\npods listed. These pods do the work to deploy and maintain the AD and validate deployment\nconfigurations.\n\n\nTo get a list of the ApigeeDeployments in your cluster, execute this command: \n\n```\nkubectl get ad -n namespace\nNAME AGE\napigee-mart-my_org 4h\napigee-runtime-my_org-my_env 4h\napigee-synchronizer-my_org-my_env 4h\napigee-udca-my_org-my_env 4h\n```"]]
