-
Notifications
You must be signed in to change notification settings - Fork 479
v1beta2: Delete .enable field from FairSharing API in config #7583
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1beta2: Delete .enable field from FairSharing API in config #7583
Conversation
✅ Deploy Preview for kubernetes-sigs-kueue ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
f843e3f to
7b6d502
Compare
|
/cc @mimowo |
7b6d502 to
2629f15
Compare
|
|
||
| func Convert_v1beta1_Configuration_To_v1beta2_Configuration(in *Configuration, out *v1beta2.Configuration, s conversionapi.Scope) error { | ||
| if in.FairSharing != nil { | ||
| out.FairSharing = &v1beta2.FairSharing{ |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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
2629f15 to
3795ea7
Compare
| 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 { |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
64f6c2f to
26c0734
Compare
|
We also deliver some samples commented out configuration, please make surr it is adjusted |
Good point. Updated. |
|
/lgtm |
|
LGTM label has been added. Git tree hash: 267097fbb9adc2903ec4e875da615ec9b5163775
|
kannon92
left a comment
There was a problem hiding this 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.
Probably need to remove this from our cert manager setup.
/hold
0938921 to
0fa88a1
Compare
You right. Thanks! Done. |
kannon92
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/hold cancel
|
LGTM label has been added. Git tree hash: fa98c44212e701766f73581d0a77bd65f3d62572
|
|
/hold |
04953c8 to
90eeee8
Compare
90eeee8 to
34a35cd
Compare
|
@mbobrovskyi Is this ready for review? I wasn't clear why you put a hold on. |
|
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 |
|
LGTM label has been added. Git tree hash: 886526aeddf0a9146449b6ec4919700d6eaaa3bc
|
|
[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 |
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?