-
Notifications
You must be signed in to change notification settings - Fork 423
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
[feat] added priorityclass syncing from host #2044
Conversation
✅ Deploy Preview for vcluster-docs canceled.Built without sensitive environment variables
|
0df84e9
to
ba45416
Compare
priorityClass.GlobalDefault = false | ||
if priorityClass.Value > 1000000000 { | ||
priorityClass.Value = 1000000000 | ||
} |
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.
Why are we doing these adjustments here, I know they are needed when going from virtual -> host, but in this case we could just leave them be, no?
if translatedValue > 1000000000 { | ||
translatedValue = 1000000000 | ||
} | ||
pObj.Value = translatedValue | ||
targetObject.Value = translatedValue |
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 this if syncing toHost, fromHost we don't mind the value
if translatedValue > 1000000000 { | ||
translatedValue = 1000000000 | ||
} | ||
targetObject.Value = translatedValue |
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.
Can you move that into the switch case and then exchange targetObject and sourceObject with the correct vObj and pObj?
865f8d5
to
5598491
Compare
What issue type does this pull request address? (keep at least one, remove the others)
/kind feature
What does this pull request do? Which issues does it resolve? (use
resolves #<issue_number>
if possible)resolves eng-4179
Please provide a short message that should be published in the vcluster release notes
Fixed an issue where vcluster ...
What else do we need to know?