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
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eApigeeDeployment (AD) is a CustomResourceDefinition (CRD) that manages the deployment, updating, and release of stateless Apigee hybrid components within a Kubernetes cluster.\u003c/p\u003e\n"],["\u003cp\u003eAD unifies previously manual hybrid resource management into an atomic deployment unit, streamlining the process.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eapigee-operators\u003c/code\u003e pod is responsible for creating, updating, and maintaining the Kubernetes and Istio resources required for AD, as well as validating the deployment configurations.\u003c/p\u003e\n"],["\u003cp\u003eYou can list all ApigeeDeployments within your cluster using the \u003ccode\u003ekubectl get ad -n namespace\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eThe current documentation version being viewed is 1.11 of the Apigee hybrid documentation.\u003c/p\u003e\n"]]],[],null,["# Apigee deployment services\n\n| You are currently viewing version 1.11 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).\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```"]]
