하이브리드 구성요소 포드의 상태를 확인합니다. 모든 구성요소 포드가 준비되면 '모든 컨테이너 준비됨' 메시지가 출력됩니다.
자동 스크립팅의 경우 컨테이너가 모두 준비되면 명령어가 상태 0으로 종료됩니다. 하나 이상의 포드가 준비되지 않은 경우 명령어가 상태 1로 종료됩니다.
지정된 조직 또는 지정된 조직 내 지정된 환경의 모든 ApigeeDeployment의 인코딩된 이름 목록을 반환합니다. 인코딩된 이름에는 조직의 해시된 이름이 있는 구성요소 이름이 포함되며, --env 플래그를 사용하면 환경의 해시된 이름이 포함됩니다. Apigee Hybrid는 네임스페이스 충돌을 방지하기 위해 조직 및 환경의 해시된 이름을 만듭니다.
--org org-name 하나 또는 --env env-name 플래그와 --org org-name 모두를 encode로 사용해야 합니다. 예를 들면 다음과 같습니다.
./apigeectl encode --org hybrid-example
List of ApigeeDeployments are:
apigee-connect-agent-hybrid-example-6a82f8a
apigee-mart-hybrid-example-6a82f8a
apigee-watcher-hybrid-example-6a82f8a
./apigeectl encode --org hybrid-example --env example-env
List of ApigeeDeployments are:
apigee-runtime-hybrid-example-example-env-9e87e2d
apigee-synchronizer-hybrid-example-example-env-9e87e2d
apigee-udca-hybrid-example-example-env-9e87e2d
apigee-logger 및 apigee-metrics와 같은 텔레메트리 구성요소의 구성을 적용합니다.
--verbose
상세 로그를 std err에 출력합니다.
예시
클러스터 구성 초기화
init를 사용하여 클러스터에 기본 요건 구성요소 구성을 적용합니다.
apply 전에 init 명령어를 실행해야 합니다.
apigeectl init -f my_overrides.yaml
클러스터 구성 적용
하이브리드 구성을 Kubernetes 클러스터에 적용하려면 apply 명령어를 사용합니다. apply을 처음 실행하면 모든 하이브리드 런타임 구성요소가 클러스터에 생성됩니다. 구성을 변경하는 경우 apply을 다시 실행하여 변경사항만 적용하거나, 플래그를 사용하여 특정 범위에만 변경사항을 적용합니다.
다음 예시에서는 하이브리드 런타임 영역 구성요소 구성을 클러스터에 적용합니다.
apigeectl apply -f my_overrides.yaml
단일 구성요소에 구성 적용
apply 명령어를 특정 구성요소로 제한하려면 apigeectl 플래그에 설명된 플래그를 사용합니다.
다음 예에서는 Cassandra 구성요소의 구성만 적용합니다.
apigeectl apply --datastore -f my_overrides.yaml
구성을 파일로 출력
설치 문제를 디버깅하는 경우 구성 설정을 검사할 수 있도록 전체 클러스터 구성을 파일에 인쇄하는 것이 유용합니다. --print-yaml 플래그는 하이브리드 구성을 stdout으로 인쇄하며 --dry-run 플래그를 사용하면 클러스터를 변경하지 않고 명령어를 실행할 수 있습니다.
[[["이해하기 쉬움","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-05(UTC)"],[[["\u003cp\u003e\u003ccode\u003eapigeectl\u003c/code\u003e is a command-line interface (CLI) used for managing Apigee hybrid in a Kubernetes cluster, requiring \u003ccode\u003ekubectl\u003c/code\u003e to be installed and configured.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eapigeectl\u003c/code\u003e commands, such as \u003ccode\u003eapply\u003c/code\u003e, \u003ccode\u003echeck-ready\u003c/code\u003e, \u003ccode\u003edelete\u003c/code\u003e, \u003ccode\u003eencode\u003c/code\u003e, \u003ccode\u003einit\u003c/code\u003e, \u003ccode\u003eversion\u003c/code\u003e and \u003ccode\u003ehelp\u003c/code\u003e, manage configurations and status of the Apigee hybrid components and cluster.\u003c/p\u003e\n"],["\u003cp\u003eScopes in \u003ccode\u003eapigeectl\u003c/code\u003e, including Storage, Environment, Organization, and Reporting, can be targeted using specific flags like \u003ccode\u003e--datastore\u003c/code\u003e, \u003ccode\u003e--all-envs\u003c/code\u003e, \u003ccode\u003e--env\u003c/code\u003e, \u003ccode\u003e--org\u003c/code\u003e, and \u003ccode\u003e--telemetry\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eapigeectl\u003c/code\u003e commands use flags like \u003ccode\u003e-f\u003c/code\u003e (\u003ccode\u003e--file-override-config\u003c/code\u003e) to specify YAML configuration files, \u003ccode\u003e--dry-run\u003c/code\u003e to preview changes, and \u003ccode\u003e--print-yaml\u003c/code\u003e to output the configuration, which are similar to their kubectl counterparts.\u003c/p\u003e\n"],["\u003cp\u003eVersion 1.4 of the documentation is end of life and should be upgraded, in addition, running \u003ccode\u003eapigeectl init\u003c/code\u003e is a necessity after fresh installs and upgrades before running \u003ccode\u003eapigeectl apply\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# apigeectl\n\n| You are currently viewing version 1.4 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`apigeectl` is a command-line interface (CLI)\nfor installing and managing Apigee hybrid in a Kubernetes cluster.\nFor\ninformation on downloading and installing `apigeectl`, see\n[Download and install apigeectl](/apigee/docs/hybrid/v1.4/install-download-install#download-and-install-apigeectl).\n| **NOTE:** You must have [`kubectl`](https://kubernetes.io/docs/reference/kubectl/overview/) installed and set up on your Kubernetes administration machine to use the `apigeectl` command.\n\nScopes for applying `apigeectl`\n-------------------------------\n\n\nBy using [`apigeectl` flags](#options) you control which scopes the command\napplies configuration changes to. For an overview of scopes within the Apigee hybrid runtime\nsee the [Runtime service configuration overview](/apigee/docs/hybrid/v1.4/service-config).\n\napigeectl syntax\n----------------\n\n```\napigeectl [command] [flags]\n```\n\nWhere:\n\n- \u003cvar translate=\"no\"\u003ecommand\u003c/var\u003e: Specifies the operation you want to\n perform. For a complete list of commands, see [apigeectl commands](#commands).\n\n- \u003cvar translate=\"no\"\u003eflags\u003c/var\u003e: Specifies command\n parameters. For a complete list of flags, see [apigeectl flags](#options).\n\napigeectl commands\n------------------\n\nThe following table lists the `apigeectl` commands:\n\napigeectl flags\n---------------\n\nThe following table lists the `apigeectl` flags:\n\n| The `apigeectl` command uses `kubectl` behind the scenes to do\n| its work. The `apigeectl` command options (`apply` and `delete`,\n| and the use of YAML configuration files, are similar to their kubectl counterparts.\n| To learn more about how objects are managed in a Kubernetes cluster, see the following topics:\n|\n| - [Imperative Management of Kubernetes Objects Using Configuration Files](https://kubernetes.io/docs/tasks/manage-kubernetes-objects/imperative-config/)\n| - [Overview of kubectl](https://kubernetes.io/docs/reference/kubectl/overview/)\n\nExamples\n--------\n\n### Initialize the cluster configuration\n\n\nApply prerequisite component configurations to your cluster with `init`.\nYou must run the `init`\ncommand before `apply`. \n\n```\napigeectl init -f my_overrides.yaml\n```\n\n### Apply the cluster configuration\n\nTo apply hybrid configurations to your Kubernetes cluster, use the\n`apply` command. The first time you run `apply` all of the\nhybrid runtime components are created in your cluster. If you make configuration changes, rerun\n`apply` to apply only the changes or use flags to apply a changes to a specific\nscope only.\n\nThe following example applies the configuration for hybrid runtime plane\ncomponents to your cluster: \n\n```\napigeectl apply -f my_overrides.yaml\n```\n\n### Apply the configuration for a single component\n\nTo restrict the `apply` command to a particular component, use the\nflags described in [apigeectl flags](#options).\n\nThe following example only applies the configuration for the Cassandra component: \n\n```\napigeectl apply --datastore -f my_overrides.yaml\n```\n\n### Print the configuration to a file\n\nIf you're debugging an installation problem, it's useful to print out the entire\ncluster configuration to a file so that you can inspect the configuration\nsettings. The `--print-yaml` flag prints\nthe hybrid configuration to stdout, and the `--dry-run` flag allows the\ncommand to run without making any changes to the cluster. \n\n```\napigeectl apply -f my_overrides.yaml --dry-run=client --print-yaml \u003e apigee-hybrid.yaml\n```\n| **NOTE:** It is a good practice to save a copy of the YAML output in source control for future reference. But be aware that the output file contains passwords and secrets that you may not want to store.\n\n### Check pod status\n\nThe following example checks the status of pods deployed to your cluster: \n\n```\napigeectl check-ready -f overrides/overrides.yaml\nAll containers ready in namespace 'my-namespace'\n```\n\n### Delete hybrid from the cluster\n\nThe following example deletes only the hybrid runtime components to your\nKubernetes cluster. To delete everything, use the `--all` flag.\n**NOTE:** To uninstall successfully, you must have `kubectl` version 1.11.x or later installed. \n\n```\napigeectl delete -f my_overrides.yaml\n```"]]
