This message was deleted.

It's tied to upstream k8s. Sometimes at max there is a week of drift but otherwise it releases when upstream does.

Our release cycle is upstream’s release cycle. We release whenever upstream releases. When they stop putting out releases for a minor, so do we. We do extensive QA on our releases, and also need to consider schedules of updates for other products that we bundle alongside Kubernetes, so our release may lag a week or more behind at times.