Clarity on konnectivity - kubernetes supported version matrix

[ipochi]

Hi @cheftako @jkh52

There isn't much clarity in the docs regarding the compatiblity matrix between konnectivity and kubernetes versions.

Example: How far back in kubernetes version can the latest tag v0.1.2 be used ?

[jkh52]

There isn't much clarity in the docs regarding the compatiblity matrix between konnectivity and kubernetes versions.

I would agree with that. But note there is some complexity here:

• kubernetes dependency on sigs.k8s.io/apiserver-network-proxy/konnectivity-client module.
  • build compatiblity
  • note that this module is only relevant in gRPC mode, not HTTPConnect
• konnectivity-client and proxy-server version compatiblity
• proxy-server and proxy-agent version compatibility

Example: How far back in kubernetes version can the latest tag v0.1.2 be used ?

#465 should resolve this question. Let's move discussion there.

[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

[jkh52]

Assigning to myself to track toward GA effort.

Related: #510 to propose predictable release cadence.