v0.24

[sbueringer]

Tasks for v0.24

• Revert excludedModules for structured-merge-diff in .gomodcheck.yaml: 🐛 Fix panic when using CRs with embedded pointer structs #3431
  • Revert: ⚠️ Bump to k8s.io/* v0.36.0-alpha.2 & implement HasSyncedChecker() #3462
• Resolve how to deal with Apply using typed apply configurations doesn't deserialize the response into the passed object #3474
• Maybe New eventsv1.Event broadcaster "object" should use the Regarding field, rather than Related #3504

[kannon92]

Will this include 0.36 bump?

We are hitting some challenges in upgrading our controllers to k8s 0.36.

kubernetes-sigs/jobset#1212 (comment)

[troy0820]

There is a PR #3506 that may go in before v0.24 is released.

[matheuscscp]

Will this include 0.36 bump?

We are hitting some challenges in upgrading our controllers to k8s 0.36.

kubernetes-sigs/jobset#1212 (comment)

Same in Flux... Our next minor needs to ship with Helm 4.2, which is about to ship in the first half of May. Helm imports c-r so I'd like to upgrade it there before 4.2 ships... Let me know if I can help with anything, would a PR be welcome? I filed one for Helm and they just merged it: helm/helm#32078 Just noticed main already has k8s 1.36 🙌 Now just praying for v0.24 to come out soon 🙏

[matheuscscp]

@sbueringer Is there an estimate for when 0.24 lands? Is there anything I can do to help? My time is all yours...

[sbueringer]

@sbueringer Is there an estimate for when 0.24 lands? Is there anything I can do to help? My time is all yours...

Just back from PTO. Thx for offering. We just have to review some PRs, otherwise we should be good. I think release should be out soon, I guess next week.

But please note that controller-runtime does not guarantee that we are releasing within a specific timeframe after the Kubernetes minor release. We are not part of the Kubernetes release cycle please try to minimize dependencies like this

[matheuscscp]

But please note that controller-runtime does not guarantee that we are releasing within a specific timeframe after the Kubernetes minor release. We are not part of the Kubernetes release cycle please try to minimize dependencies like this

Thanks @sbueringer, I fully understand. We don't normally have too many problems with this on every minor, and we do only 3 minors per year. We need to follow k8s and helm besides controller-runtime, since all of these are super core for us. We do this just like helm, whose releases follow k8s. Neither flux or helm are part of the Kubernetes release cycle, but also neither of us has a choice. Our dependency on these projects is not like depending on a random timestamp parser or something like, that that we could easily remove.

The big problem this time is k8s shipping these many breaking changes. The less they do this, the less chaos we have across the ecosystem. This time we got really unlucky. Since k8s is on the bottom of all these core components of the ecosystem, it's really important for everybody for these to be aligned in terms of k8s version.

If time and hands is what is missing for controller-runtime to be able to support the Kubernetes ecosystem on situations like this, I'm more than happy to give my personal time. Please let me know how I can help in these situations, you can ping me to review any PRs and things like that. As I said, my time is all yours.