NOTE: Some aspects of this product are in Beta. The hybrid installation options are GA. To join the Beta program, reach out to your Apigee representative.

Apigee deployment services

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-deployment-controller Apigee Deployment Controller is a Kubernetes custom controller that 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. See also adc and adah in the Configuration property reference.
apigee-deployment-admissionhook Apigee Admission Hook is a service used to validate the ApigeeDeployment configuration before persisting it in Kubernetes cluster. For example, the Admission Hook validates fields. See also What are admission webhooks. See also adah in the Configuration property reference.

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