Skip to content

Conversation

@mbobrovskyi
Copy link
Contributor

@mbobrovskyi mbobrovskyi commented Nov 7, 2025

What type of PR is this?

/kind cleanup
/kind api-change

What this PR does / why we need it:

Delete .enable field from FairSharing API in config.

Which issue(s) this PR fixes:

Fixes #5032

Special notes for your reviewer:

Does this PR introduce a user-facing change?

v1beta2: Delete .enable field from FairSharing API in config

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API labels Nov 7, 2025
@netlify
Copy link

netlify bot commented Nov 7, 2025

Deploy Preview for kubernetes-sigs-kueue ready!

Name Link
🔨 Latest commit 34a35cd
🔍 Latest deploy log https://app.netlify.com/projects/kubernetes-sigs-kueue/deploys/69158e9f76f277000866c7ec
😎 Deploy Preview https://deploy-preview-7583--kubernetes-sigs-kueue.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Nov 7, 2025
@mbobrovskyi mbobrovskyi force-pushed the cleanup/delete-enable-field-from-FairSharing-API-in-config branch from f843e3f to 7b6d502 Compare November 7, 2025 15:57
@mbobrovskyi
Copy link
Contributor Author

/cc @mimowo

@k8s-ci-robot k8s-ci-robot requested a review from mimowo November 7, 2025 15:57
@mbobrovskyi mbobrovskyi force-pushed the cleanup/delete-enable-field-from-FairSharing-API-in-config branch from 7b6d502 to 2629f15 Compare November 7, 2025 16:16
@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Nov 7, 2025

func Convert_v1beta1_Configuration_To_v1beta2_Configuration(in *Configuration, out *v1beta2.Configuration, s conversionapi.Scope) error {
if in.FairSharing != nil {
out.FairSharing = &v1beta2.FairSharing{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should only do it if enabled in v1beta1. Otherwise if the admin disables in v1beta1, then we will use it in 0.15

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please also there is a test which would pick up the initial bug

@mbobrovskyi mbobrovskyi force-pushed the cleanup/delete-enable-field-from-FairSharing-API-in-config branch from 2629f15 to 3795ea7 Compare November 7, 2025 16:30
return autoConvert_v1beta1_Configuration_To_v1beta2_Configuration(in, out, s)
}

func Convert_v1beta2_Configuration_To_v1beta1_Configuration(in *v1beta2.Configuration, out *Configuration, s conversionapi.Scope) error {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we really need conversions for config apis?

The config API is not a CRD so I don't quite understand how a conversion would actually happen.

This is mainly translated to a config map.

So I guess someone specifiy v1beta1 in a helm chart would potentially be converted? But I don't quite understand where that would occur.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They are very useful for smooth transition. For example, currently users have in configMaps v1beta1 version. When they install new Kueue they may still need time to migrate the configMap, so they could start by reading v1beta1, and then convert to v1beta2 as a follow up.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Most of the code is auto generated anyway, so I don't think maintaining is much cost

Copy link
Contributor Author

@mbobrovskyi mbobrovskyi Nov 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, if the user is still using v1beta1, we need to convert it to v1beta2, since the codebase uses the v1beta2 version everywhere.

Copy link
Contributor

@kannon92 kannon92 Nov 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But without a CRD who does the conversion?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried installing Kueue with v1beta1, but it didn’t work because the conversions are missing.

Copy link
Contributor

@mimowo mimowo Nov 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The conversion is applied when loading the configuration in main.go. It is not handled by webhooks.

@mbobrovskyi mbobrovskyi force-pushed the cleanup/delete-enable-field-from-FairSharing-API-in-config branch 3 times, most recently from 64f6c2f to 26c0734 Compare November 7, 2025 17:10
@mimowo
Copy link
Contributor

mimowo commented Nov 7, 2025

We also deliver some samples commented out configuration, please make surr it is adjusted

@mbobrovskyi
Copy link
Contributor Author

We also deliver some samples commented out configuration, please make surr it is adjusted

Good point. Updated.

@mimowo
Copy link
Contributor

mimowo commented Nov 7, 2025

/lgtm
/approve
assymung the tests pass

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 7, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 267097fbb9adc2903ec4e875da615ec9b5163775

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 7, 2025
Copy link
Contributor

@kannon92 kannon92 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Test failure is legit.

https://github.com/kubernetes-sigs/kueue/blob/main/test/e2e/config/certmanager/controller_manager_config.yaml#L15

Probably need to remove this from our cert manager setup.

/hold

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 7, 2025
@k8s-ci-robot k8s-ci-robot requested a review from mimowo November 8, 2025 03:41
@mbobrovskyi mbobrovskyi force-pushed the cleanup/delete-enable-field-from-FairSharing-API-in-config branch 2 times, most recently from 0938921 to 0fa88a1 Compare November 9, 2025 07:08
@mbobrovskyi
Copy link
Contributor Author

Probably need to remove this from our cert manager setup.

You right. Thanks! Done.

Copy link
Contributor

@kannon92 kannon92 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 10, 2025
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 10, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: fa98c44212e701766f73581d0a77bd65f3d62572

@mbobrovskyi
Copy link
Contributor Author

/hold

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 10, 2025
@mbobrovskyi mbobrovskyi force-pushed the cleanup/delete-enable-field-from-FairSharing-API-in-config branch from 04953c8 to 90eeee8 Compare November 12, 2025 07:48
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 12, 2025
@mbobrovskyi mbobrovskyi force-pushed the cleanup/delete-enable-field-from-FairSharing-API-in-config branch from 90eeee8 to 34a35cd Compare November 13, 2025 07:54
@kannon92
Copy link
Contributor

@mbobrovskyi Is this ready for review?

I wasn't clear why you put a hold on.

@mbobrovskyi
Copy link
Contributor Author

mbobrovskyi commented Nov 13, 2025

Oh, we’re still waiting for the final decision from @mimowo and @mwysokin on whether this is the correct way to remove enabled field — that’s why it’s still on hold.

@mimowo
Copy link
Contributor

mimowo commented Nov 13, 2025

Let me actually merge, we can still revert that change if someone raises objections, so far I haven't heard any. This way we can also avoid conflicts with other PRs
/unhold
/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Nov 13, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 886526aeddf0a9146449b6ec4919700d6eaaa3bc

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mbobrovskyi, mimowo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit 8b6a908 into kubernetes-sigs:main Nov 13, 2025
22 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v0.15 milestone Nov 13, 2025
@mbobrovskyi mbobrovskyi deleted the cleanup/delete-enable-field-from-FairSharing-API-in-config branch November 13, 2025 17:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

v1beta2: Delete .enable field from FairSharing API in config

4 participants