You have now installed the structure for Apigee hybrid. Next you will check the readiness of
your Kubernetes cluster before installing the Apigee Helm charts.
123456789(NEXT) Step 10: Check cluster readiness1112
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eThis document provides instructions for installing Custom Resource Definitions (CRDs) for Apigee hybrid, a process which requires elevated cluster permissions.\u003c/p\u003e\n"],["\u003cp\u003eThe only supported method for installing Apigee CRDs involves using the \u003ccode\u003ekubectl apply -k\u003c/code\u003e command with specific parameters, from the \u003ccode\u003e$APIGEE_HELM_CHARTS_HOME\u003c/code\u003e directory and the use of \u003ccode\u003e--server-side\u003c/code\u003e, while avoiding standard \u003ccode\u003ekubectl apply\u003c/code\u003e operations.\u003c/p\u003e\n"],["\u003cp\u003eInstallation begins with a dry-run using \u003ccode\u003ekubectl apply -k\u003c/code\u003e with \u003ccode\u003e--dry-run=server\u003c/code\u003e to preview the changes before applying them, followed by the actual installation using the same command without the dry-run flag.\u003c/p\u003e\n"],["\u003cp\u003eAfter the installation, the success can be confirmed by checking the output of the \u003ccode\u003ekubectl get crds\u003c/code\u003e command and ensuring that the Apigee CRDs are listed.\u003c/p\u003e\n"]]],[],null,["# Step 9: Install the Apigee hybrid CRDs\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\nThis step explains how to install the Custom Resource Definitions (CRDs) for Apigee hybrid.\n\nInstall the Apigee CRDs:\n------------------------\n\n| **Note:** From this step onwards, all commands should be run from `$APIGEE_HELM_CHARTS_HOME` directory.\n| **Note:** This is the only supported method for installing Apigee CRDs. Do not use `kubectl apply` without `-k`, do not omit `--server-side`.\n| **Note:** This step requires elevated cluster permissions.\n\n1. Perform a dry-run of the installation by running\n the following command:\n\n ```\n kubectl apply -k apigee-operator/etc/crds/default/ \\\n --server-side \\\n --force-conflicts \\\n --validate=false \\\n --dry-run=server\n ```\n2. After checking the installation with `--dry-run`, install the Apigee CRDs with\n the following command:\n\n ```\n kubectl apply -k apigee-operator/etc/crds/default/ \\\n --server-side \\\n --force-conflicts \\\n --validate=false\n ```\n3. Validate the installation with the `kubectl get crds` command: \n\n ```\n kubectl get crds | grep apigee\n ```\n\n Your output should look something like the following: \n\n ```\n apigeedatastores.apigee.cloud.google.com 2023-10-09T14:48:30Z\n apigeedeployments.apigee.cloud.google.com 2023-10-09T14:48:30Z\n apigeeenvironments.apigee.cloud.google.com 2023-10-09T14:48:31Z\n apigeeissues.apigee.cloud.google.com 2023-10-09T14:48:31Z\n apigeeorganizations.apigee.cloud.google.com 2023-10-09T14:48:32Z\n apigeeredis.apigee.cloud.google.com 2023-10-09T14:48:33Z\n apigeerouteconfigs.apigee.cloud.google.com 2023-10-09T14:48:33Z\n apigeeroutes.apigee.cloud.google.com 2023-10-09T14:48:33Z\n apigeetelemetries.apigee.cloud.google.com 2023-10-09T14:48:34Z\n cassandradatareplications.apigee.cloud.google.com 2023-10-09T14:48:35Z\n ```\n\n| **Note:** You may see warnings about deprecated terms. This will not impact the installation of the Apigee hybrid CRDs.\n\n\nYou have now installed the structure for Apigee hybrid. Next you will check the readiness of\nyour Kubernetes cluster before installing the Apigee Helm charts.\n\n\n[1](/apigee/docs/hybrid/v1.11/helm-install-create-cluster)\n\n\n[2](/apigee/docs/hybrid/v1.11/helm-install-download-charts)\n\n\n[3](/apigee/docs/hybrid/v1.11/helm-install-create-namespace)\n\n\n[4](/apigee/docs/hybrid/v1.11/helm-install-service-accounts)\n\n\n[5](/apigee/docs/hybrid/v1.11/helm-install-create-tls-certificates)\n\n\n[6](/apigee/docs/hybrid/v1.11/helm-install-create-overrides)\n\n\n[7](/apigee/docs/hybrid/v1.11/helm-install-enable-synchronizer-access)\n\n\n[8](/apigee/docs/hybrid/v1.11/helm-install-cert-manager)\n\n\n[9](/apigee/docs/hybrid/v1.11/helm-install-crds)\n\n\n[(NEXT) Step 10: Check cluster readiness](/apigee/docs/hybrid/v1.11/helm-install-check-cluster)\n\n\n[11](/apigee/docs/hybrid/v1.11/helm-install-helm-charts)\n\n\n[12](/apigee/docs/hybrid/v1.11/helm-install-workload-identity)"]]
