[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-03-12。"],[[["Apigee hybrid supports Helm version 3.14.2 and above for managing its components."],["Apigee hybrid components are installed and managed using specific Helm charts, including `apigee-operator`, `apigee-datastore`, `apigee-redis`, `apigee-telemetry`, `apigee-ingress-manager`, `apigee-org`, `apigee-env`, and `apigee-virtualhost`."],["The `apigeectl init` command is mimicked in Helm by installing or upgrading the `apigee-operator` and `apigee-ingress-manager` charts, which requires the Apigee CRDs to be installed first."],["There is no single Helm command to manage all Apigee hybrid components at once, as each component needs to be installed or upgraded individually using its corresponding chart, similarly there is no single Helm command to delete all components."],["Equivalent Helm commands, like `helm install` or `helm upgrade`, are available for most `apigeectl` commands such as `apply`, `delete`, or `dry-run`, enabling granular control over individual components, while `apigeectl check-ready` does not have an exact equivalent command, but relies on checking cluster readiness."]]],[]]