cluster-api-provider-gcp
cluster-api-provider-gcp copied to clipboard
kubernetes-sigs
Cloud Controller Manager
/kind feature
Describe the solution you'd like
This provider uses the in-tree gce cloud provider integration with kubelet (--cloud-provider=gce).
It has been deprecated in Kubernetes v1.29 and will eventually be removed.
=> This provider should include in its template a deployment of GCP Cloud Controller.
Anything else you would like to add:
A sample deploy manifest is provided by this controller here.
Hello, for what is worth this workaround: DisableCloudProviders=false,DisableKubeletCloudCredentialProviders=false is not accepted anymore from 1.31.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Encoutered this issue too, any plan to do a chart for the ccm & csi-drivers ?
Thanks for the heads up @spnngl @mloiseleur. We're looking at this issue and hope to have it fixed soon.
BTW, there is already an e2e test using it: https://github.com/kubernetes-sigs/cluster-api-provider-gcp/blob/main/test/e2e/data/ccm/gce-cloud-controller-manager.yaml
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle rotten - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The field was removed from templates here but we should also include the CCM in the template, as other providers do, via ClusterResourceSet: https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/4eade90610937e65331047e9fec376003af7f2ce/templates/cluster-template.yaml#L150
/remove-lifecycle-rotten