cluster-api-provider-gcp icon indicating copy to clipboard operation
cluster-api-provider-gcp copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Move managed cluster support (GKE) to general availability

Open salasberryfin opened this issue 1 year ago • 6 comments
trafficstars

/kind feature

Describe the solution you'd like

As of today, support for provisioning GKE clusters is still an experimental feature and has been for a number of months.

In recent community meetings we discussed the viability of moving GKE support out of the experimental folder and into general availability. This would allow CAPG to follow other providers, such as CAPA and CAPZ which have full support for their corresponding managed clusters: CAPA, CAPZ.

The promotion of GKE to stable could be a major step towards a more feature rich and stable CAPG, and we could push to add support for existing GKE functionalities that are still not covered by the provider (there are a few related PRs).

Since this is an important change, we thought it would be great to create this issue where we can discuss pros/cons and plan what needs to be done if we decide to go ahead.

Initially, this seems to be a non-breaking change for the API, since it means adding types but not modifying existing ones, but it would be great to have feedback from those that are more knowledgeable of the codebase.

Anything else you would like to add:

As a follow up to this, ClusterClass support for managed clusters would be one of the relevant features we could be adding, as non-managed GCP clusters can already be provisioned from a class (refer to this) and this is expected to become a powerful/distinctive functionality of CAPI.

Please, feel free to share your thoughts on this.

Related issues

  • [x] https://github.com/kubernetes-sigs/cluster-api-provider-gcp/issues/1387
  • [x] https://github.com/kubernetes-sigs/cluster-api-provider-gcp/issues/1309

salasberryfin avatar Mar 07 '24 18:03 salasberryfin

@salasberryfin is looking for some feedback on this one from core maintainers /assign @richardcase @cpanato

damdo avatar Apr 04 '24 16:04 damdo

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/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was 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

k8s-triage-robot avatar Jul 03 '24 16:07 k8s-triage-robot

/remove-lifecycle stale

salasberryfin avatar Jul 04 '24 07:07 salasberryfin

Looking at unblocking this and moving the feature out of experimental.

Let's collect a list of PRs related to managed clusters that we should address:

  • [ ] https://github.com/kubernetes-sigs/cluster-api-provider-gcp/pull/1024
  • [ ] https://github.com/kubernetes-sigs/cluster-api-provider-gcp/pull/901
  • [ ] https://github.com/kubernetes-sigs/cluster-api-provider-gcp/pull/1133
  • [ ] https://github.com/kubernetes-sigs/cluster-api-provider-gcp/pull/1134

Feel free to contribute to the list with other relevant PRs/issues.

cc: @richardcase @damdo @cpanato

salasberryfin avatar Sep 06 '24 06:09 salasberryfin

/lifecycle frozen

richardcase avatar Nov 07 '24 17:11 richardcase

/area gke

richardcase avatar Nov 07 '24 17:11 richardcase