[[["이해하기 쉬움","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-03-12(UTC)"],[[["This documentation pertains to Apigee hybrid version 1.5, which is end-of-life, and users should upgrade to a newer version."],["Installation of Apigee hybrid requires navigating to the `hybrid-base-directory`/`hybrid-files` directory and ensuring `kubectl` is set to the correct context for the target cluster."],["Prior to full execution, it is advised to perform a dry run of both the `init` and `apply` commands, with the syntax of the `--dry-run` flag depending on the version of `kubectl` being used."],["The `init` command installs the Apigee Deployment Controller and Apigee Admission Webhook, and after which you should apply the Apigee-specific runtime components using the `apply` command."],["Deployment status can be monitored using `$APIGEECTL_HOME/apigeectl check-ready` and `kubectl get pods` commands, and the installation is considered complete when all pods are ready."]]],[]]