Upgrade cronjobs from batch/v1beta to batch/v1

Question

Upgrade cronjobs from batch/v1beta to batch/v1

anuragpathak21 opened this issue a year ago · comments

Anurag commented a year ago

Version 1.21 of kubernetes promoted cron jobs from batch/v1beta to batch/v1

Upgrade cronjobs from batch/v1beta to use batch/v1

Chris Bono · Answer 1 · Thu Mar 23 2023 23:08:50 GMT+0800 (China Standard Time)

Some background info on the current API (v125)

https://kubernetes.io/docs/reference/using-api/deprecation-guide/#cronjob-v125

Anurag · Answer 2 · Mon Mar 27 2023 07:40:16 GMT+0800 (China Standard Time)

@onobc Due to removal of batch/v1beta1 from V1.25 we are unable to use SCDF in our cluster with version 1.25.

Chris Bono · Answer 3 · Mon Mar 27 2023 21:12:38 GMT+0800 (China Standard Time)

@anuragpathak21 - I understand. Sorry, if my comment w/ link (but w/o any context) was confusing. It was meant as an internal note to lookup the latest details of the API. I meant to add some context w/ the link.

We are looking into this issue currently and should have a direction in the next couple days.

Mark Pollack · Answer 4 · Tue Mar 28 2023 21:32:46 GMT+0800 (China Standard Time)

I am waiting to hear back from our commercial customers and we will update you shortly. I'd expect we make the update in the next point release FWIW.

Just out of curiosity, are you aware of the features that are available only in our commercial offering?

https://docs.vmware.com/en/VMware-Spring-Cloud-Data-Flow-for-Kubernetes/1.5/scdf-k8s/GUID-pro-features-index.html

Chris Bono · Answer 5 · Thu Mar 30 2023 01:32:06 GMT+0800 (China Standard Time)

We are unable to make this change in 2.10 as we can not exclude k8s version 1.19,1.20 in SCDF 2.10.

We will make this change in 2.11 and the k8s compatibility will look as follows:

2.11 will support k8s 1.21 - 1.25
2.10 supports k8s < 1.25

The next question is when will 2.11 be available. We are working on it currently and will firm up some milestone dates soon.

dclangan · Answer 6 · Mon Apr 10 2023 23:29:36 GMT+0800 (China Standard Time)

@onobc What is the best way to get updates regarding timing for 2.11 release?

Chris Bono · Answer 7 · Tue Apr 11 2023 01:56:18 GMT+0800 (China Standard Time)

Hi @dclangan .

This week the team will assign issues and a date to the 2.11.0 milestone.

The best way to "track" is the date on the milestone and the issues still in open status on the milestone.

Somewhat unrelated - but good to know... note that we have:

created a mini-mono-repo for all deployers #529
converted https://github.com/spring-cloud/spring-cloud-dataflow into a mini-mono-repo for all other SCDF pieces.

Reto Gantenbein · Answer 8 · Mon Apr 24 2023 15:09:05 GMT+0800 (China Standard Time)

Any update on the date for the 2.11.0 release? We are currently stuck rolling out OpenShift updates due to this issue.

Chris Bono · Answer 9 · Mon Apr 24 2023 22:40:27 GMT+0800 (China Standard Time)

Hi @ganto
We got pulled off on other issues last week and did not get a chance to firm up the dates. We should have a date set in the next few days.

Thanks

Chris Bono · Answer 10 · Thu Apr 27 2023 02:39:45 GMT+0800 (China Standard Time)

We have an estimated release date of 5/17/2023.

Vibhor Mahajan · Answer 11 · Sun Jun 11 2023 01:06:55 GMT+0800 (China Standard Time)

Hello, @onobc, is there a revised ETA on this release?

Chris Bono · Answer 12 · Sun Jun 11 2023 01:13:35 GMT+0800 (China Standard Time)

Hello @v1bh0r , yes the date was moved to 2023-06-20. I mentioned in my reply on the duplicate issue but it is a good thing to callout here as the ETA was previously mentioned above. Thanks.

The fix is in the 2.11.0-SNAPSHOT if you want to try it out.

Vibhor Mahajan · Answer 13 · Tue Jun 20 2023 19:25:40 GMT+0800 (China Standard Time)

Hello @onobc , we are eagerly awaiting the 2.11 release today. Just in case the release gets delayed, can you point me in the right direction to build the docker image for the 2.11 codebase and deploy it as a part of the cluster deployed using the bitnami charts?