**What steps did you take and what happened:** Attempting to install the Helm chart for `cluster-api-operator` results in a flaky installation process. The `CRDs` are located in the `templates/operator-components.yaml` file instead of the `crds` directory. ```sh helm upgrade --install cluster-api-operator-docker cluster-api-operator/cluster-api-operator --version 0.10.1 -n cluster-api-operator-docker --create-namespace --values ./cluster-api-operator-values.yaml Release "cluster-api-operator-docker" does not exist. Installing it now. Error: failed post-install: warning: Hook post-install cluster-api-operator/templates/core-conditions.yaml failed: 1 error occurred: * Internal error occurred: failed calling webhook "vcoreprovider.kb.io": failed to call webhook: Post "https://capi-operator-webhook-service.cluster-api-operator-docker.svc:443/mutate-operator-cluster-x-k8s-io-v1alpha2-coreprovider?timeout=10s": no endpoints available for service "capi-operator-webhook-service" ``` **What did you expect to happen:** The Helm install should complete successfully without errors. **Anything else you would like to add:** It is possible to separate the `CustomResourceDefinitions` from the other components using commands like the following: ```sh cat operator-components.yaml | yq 'select(.kind != "CustomResourceDefinition")' cat operator-components.yaml | yq 'select(.kind == "CustomResourceDefinition")' ``` Can we consider reorganizing the files accordingly? **Environment:** - Cluster-api-operator version: - Cluster-api version: - Minikube/KIND version: - Kubernetes version: (use `kubectl version`): - OS (e.g. from `/etc/os-release`): /kind bug [One or more /area labels. See https://github.com/kubernetes-sigs/cluster-api-operator/labels?q=area for the list of labels] --- Feel free to fill in the specific versions and any additional environment details before submitting the issue.