This step explains how to install the Custom Resource Definitions (CRDs) for Apigee hybrid.
Install the Apigee CRDs:
-
If you are installing Apigee Hybrid into a different namespace than the default (
apigee
), editapigee-operators/etc/crds/default/kustomization.yaml
and change the namespace to match:namespace: APIGEE_NAMESPACE
For example:
namespace: my-namespace
-
Perform a dry-run of the installation by running the following command:
kubectl apply -k apigee-operator/etc/crds/default/ \ --server-side \ --force-conflicts \ --validate=false \ --dry-run=server
-
After checking the installation with
--dry-run
, install the Apigee CRDs with the following command:kubectl apply -k apigee-operator/etc/crds/default/ \ --server-side \ --force-conflicts \ --validate=false
- Validate the installation with the
kubectl get crds
command:kubectl get crds | grep apigee
Your output should look something like the following:
apigeedatastores.apigee.cloud.google.com 2024-12-16T19:44:48Z apigeedeployments.apigee.cloud.google.com 2024-12-16T19:44:49Z apigeeenvironments.apigee.cloud.google.com 2024-12-16T19:44:50Z apigeeissues.apigee.cloud.google.com 2024-12-16T19:44:52Z apigeeorganizations.apigee.cloud.google.com 2024-12-16T19:44:53Z apigeeredis.apigee.cloud.google.com 2024-12-16T19:44:55Z apigeerouteconfigs.apigee.cloud.google.com 2024-12-16T19:44:56Z apigeeroutes.apigee.cloud.google.com 2024-12-16T19:44:56Z apigeetelemetries.apigee.cloud.google.com 2024-12-16T19:44:58Z cassandradatareplications.apigee.cloud.google.com 2024-12-16T19:45:00Z secretrotations.apigee.cloud.google.com 2024-12-16T19:45:00Z
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.