Release gke-gcloud-auth-plugin separately in this repo similar to how aws-iam-authenticator is released.

[upodroid]

Installing gke-gcloud-auth-plugin is very hard(as in too many extra deps) today as you would need to install it either via apt or install the entire gcloud SDK as described here. https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke

The code lives in this repo, it shouldn't be hard to attach a goreleaser to it and release it.

https://github.com/kubernetes/cloud-provider-gcp/tree/master/cmd/gke-gcloud-auth-plugin

I need to add the binary to an alpine image and it is proving tricky as Google doesn't release all the goarchs that we need.

https://github.com/GoogleCloudPlatform/cloud-sdk-docker/blob/master/Dockerfile (for some reason, this is an amd64 image only 😒 )

https://packages.cloud.google.com/apt/dists/cloud-sdk-bullseye/main

kubernetes/test-infra#28277
kubernetes/test-infra#28142

https://issuetracker.google.com/issues/263033287

@aojea what do you think?

[aojea]

I'm not really familiar with the workflows in this repo and its constraints to publish binaries,
maybe @mikedanese knows better?

[BenTheElder]

@aojea anyone else that might know?

[sftim]

/sig release

[BenTheElder]

I don't think this is in scope for SIG Release as an out of tree binary. Subprojects are responsible for their own releases.

[BenTheElder]

It's a bit early still but there are binaries uploaded to staging on postsubmit as of today. It needs more cleanup and then they can be promoted with file promoter hopefully.

Been following up with @ndixita and @aojea on this.

[upodroid]

@justinsb ^

[k8s-triage-robot]

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]

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/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 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

[BenTheElder]

/lifecycle frozen

[BenTheElder]

I lost track of exactly what happened here but I think these are being copied to staging at least.

The gap around advertising releases remains and is something I'm discussing with the involved teams.