Allow for provider CRs in the same helm chart as the operator about cluster-api-operator HOT 3 OPEN

Thanks for describing the issue. What about using a post-install hook for applied CRs like this:

apiVersion: operator.cluster.x-k8s.io/v1alpha1
kind: CoreProvider
metadata:
  name: cluster-api
  namespace: capi-system
  annotations:
    "helm.sh/hook": post-install

then you can run helm install with --wait flag and it will apply CRs after CRDs and all other components are created. I'm already working on a PR for "quickstart" bootstrapping of management cluster using helm.

from cluster-api-operator.

Thanks for describing the issue. What about using a post-install hook for applied CRs like this:

apiVersion: operator.cluster.x-k8s.io/v1alpha1
kind: CoreProvider
metadata:
  name: cluster-api
  namespace: capi-system
  annotations:
    "helm.sh/hook": post-install

then you can run helm install with --wait flag and it will apply CRs after CRDs and all other components are created. I'm already working on a PR for "quickstart" bootstrapping of management cluster using helm.

If I'm not mistaken, that would also fail validations during the first install (or any update that introduces new fields) since I believe the post-install hooks are also validated before any resource is applied.

It's possible that I'm missing something though 😃

from cluster-api-operator.

/triage accepted

from cluster-api-operator.