Will the CRD’s v1beta1 of the master branch change before release-0.3.0 is released?

[fjding]

Hi, I found that there is a big difference between v1alpha2 and v1beta1. I want to know whether the crd of v1beta1 has been confirmed? Will there be changes before release-0.3.0?

[fjding]

We plan to use kueue as the batch scheduling component, but found that v1alpha2 is outdated, so we want to use the master branch as the online version.

[tenzen-y]

Thank you for creating this issue!

We plan to include v1beta1 in release-0.3.0.

#360

I want to know whether the crd of v1beta1 has been confirmed?

Does that mean you want to know that v1beta1 is tested? If so, we confirmed v1beta1 using the KinD cluster.

#604

[fjding]

I want to know whether the crd of v1beta1 has been confirmed?

Does that mean you want to know that v1beta1 is tested? If so, we confirmed v1beta1 using the KinD cluster.

#604
I means whether the structure of the CRD will have any change before release 0.3.0?

[tenzen-y]

We will not release any patch versions for v0.2. So you can deploy v1beta1 using the main branch or v0.3.0.

cc: @alculquicondor @kerthcet

[alculquicondor]

If you have a big need for some patches in v0.2, please send the cherry-picks and we can add a new release.

But our efforts are on v0.3, and yes, it's not backwards compatible. I would appreciate it if you can be an early adopter of v0.3. My plan is to have a release by the end of next week.

[alculquicondor]

/close

[k8s-ci-robot]

@alculquicondor: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.