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
cass-operator is currently pinned to the go dependencies for k8s 1.29.
There is a breaking change in a newer k8s.io/controller-runtime version that prevents us from upgrading our own repo to >= k8s 1.30 because of the diamond dependency problem.
k8s 1.31 was released in August and 1.32 is due in December. It would be great to upgrade cass-operator's k8s.io dependencies to 1.31.
1.23 is going to be released this week, so the cycle for 1.24 starts after that. I don't have exact promised schedule (end of the year is tricky), but I'm trying to target before Christmas holidays.
What is missing?
cass-operator is currently pinned to the go dependencies for k8s 1.29.
There is a breaking change in a newer k8s.io/controller-runtime version that prevents us from upgrading our own repo to >= k8s 1.30 because of the diamond dependency problem.
k8s 1.31 was released in August and 1.32 is due in December. It would be great to upgrade cass-operator's k8s.io dependencies to 1.31.
The breaking change that will require additional changes to cass-operator is in controller-runtime v0.18.0. The pkg/config package is removed and users are asked to define their own configuration. This package is currently referenced in apis/config/v1beta1, so a new config implementation will need to be added to replace this.
Why is this needed?
Updating to latest k8s.io dependencies allows users to use newer k8s.io functionality.
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: CASS-73
The text was updated successfully, but these errors were encountered: