kops icon indicating copy to clipboard operation
kops copied to clipboard
verified publisher icon kubernetes

Let's write down a policy for go version updates

Open justinsb opened this issue 6 months ago • 3 comments

I'm not sure if we have written down the policy, but in our LLM-guided future it would be great to write down:

  • When we update go minor versions (especially for backports)
  • When we update other dependencies (and I suspect here we have a different policy for backports)

justinsb avatar Jun 22 '25 15:06 justinsb

cc @hakman @rifelpet

justinsb avatar Jun 22 '25 15:06 justinsb

I think a reasonable starting point is to have a kops release's go minor version match that of its k/k dependencies.

rifelpet avatar Jun 23 '25 23:06 rifelpet

We could also upgrade all supported versions, including master, when k/k cherry-picks the new Go version. (unless there is some amazing feature that we want to use very fast).

hakman avatar Jun 24 '25 13:06 hakman

Seem that's it's pretty hard to not bump Go. After some time, dependencies start pulling the latest k8s version and latest Go comes with it.

hakman avatar Jun 27 '25 14:06 hakman

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 Oct 10 '25 16:10 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

k8s-triage-robot avatar Nov 09 '25 16:11 k8s-triage-robot