Alexander Demicev
Alexander Demicev
I think the solution might require CLI to discover that cilium is being deployed to openshift
Never mind my previous comment, looks like the cluster name is being discovered from the current context of the kubeconfig. ``` contexts: - context: cluster: mycluster user: myuser name: myuser...
This suggestion seems useful
Hi, I'm interested in implementing support for ignition files.
@richardcase gcp cluster controller also tries to populate the failure domain field https://github.com/kubernetes-sigs/cluster-api-provider-gcp/blob/main/controllers/gcpcluster_controller.go#L179-L196 but regardless of that, if the payload is invalid it's better to fail somewhere on the GCP...
https://docs.google.com/document/d/1odiy0k_KZngdhidN_ll9Mb8WgGUR9iMFU7NfYRZKCvA/edit
+1 from me, thanks for all your contributions to cloud providers.
Seems like the issue is resolved by introduction of a bump bot in homebrew, see this thread for context https://kubernetes.slack.com/archives/C8TSNPY4T/p1673372872896449?thread_ts=1673227707.288409&cid=C8TSNPY4T
Github token can be added to the provider secret, it's documented here https://github.com/kubernetes-sigs/cluster-api-operator/tree/main/docs#installing-azure-infrastructure-provider. I guess we need to highlight it better.
@dependabot rebase