[[["わかりやすい","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-08-18 UTC。"],[[["\u003cp\u003eThis document outlines the steps to install Apigee hybrid version 1.11 into a cluster, beginning with navigating to the \u003ccode\u003ehybrid-base-directory\u003c/code\u003e/\u003ccode\u003ehybrid-files\u003c/code\u003e directory.\u003c/p\u003e\n"],["\u003cp\u003eThe installation process involves verifying the \u003ccode\u003ekubectl\u003c/code\u003e context, optionally setting the \u003ccode\u003eKUBECONFIG\u003c/code\u003e variable for specific platforms, and performing dry runs before initializing and applying the configuration.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003einit\u003c/code\u003e command installs the Apigee Deployment Controller and Admission Webhook, while the \u003ccode\u003eapply\u003c/code\u003e command deploys the Apigee-specific runtime components to the cluster, and it is important to periodically check the status of the pods until they are ready.\u003c/p\u003e\n"],["\u003cp\u003eFor GKE installations using Workload Identity, the next step will be to configure the associations between Kubernetes service accounts and Google service accounts, whereas for other installations, the next step will be configuring the Apigee ingress gateway.\u003c/p\u003e\n"]]],[],null,[]]