You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an issue to help us remember the policy (see #2591, #2979) to allow ourselves to drop support for k8s versions as long as major cloud providers has stopped supporting them.
I suggest drop support as part of the z2jh 3.0.0 release if it happens before 01 May. At worst someone will be forced to upgrade the k8s cluster a month or so before it reached EOL in the managed cloud provider service if they want to update to the new z2jh version directly as well.
The key benefit of dropping a bit earlier is that we reduce complexity for maintenance of this helm chart, and that we avoid making another breaking release.
The text was updated successfully, but these errors were encountered:
This is an issue to help us remember the policy (see #2591, #2979) to allow ourselves to drop support for k8s versions as long as major cloud providers has stopped supporting them.
I suggest drop support as part of the z2jh 3.0.0 release if it happens before 01 May. At worst someone will be forced to upgrade the k8s cluster a month or so before it reached EOL in the managed cloud provider service if they want to update to the new z2jh version directly as well.
The key benefit of dropping a bit earlier is that we reduce complexity for maintenance of this helm chart, and that we avoid making another breaking release.
The text was updated successfully, but these errors were encountered: