-
Notifications
You must be signed in to change notification settings - Fork 170
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
upgrade gatekeeper to version 3.11.1 #2954
Conversation
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'm a little disconnected from GK, so I left a few questions - nothing here that is very concerning on it's face, I'm just not really sure what I'm looking at to be honest :p
@@ -41,11 +41,11 @@ const ( | |||
|
|||
defaultManagerRequestsCPU = "100m" | |||
defaultManagerLimitCPU = "1000m" | |||
defaultManagerRequestsMem = "256Mi" | |||
defaultManagerRequestsMem = "512Mi" |
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.
out of curiosity - is this following a recommendation per the version bump, or something unrelated?
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.
Hi @yjst2012 I am also curious about this. Because it will have impact on a scheduler and the masters are of a fixed size.
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.
yep, this change is made by gatekeeper. well basically all stuff here is porting from upstream.
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.
Is everything under staticresources
auto-generated or is this something that needs thorough review?
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.
no, it is a manual step, ie, compare the changed made to the upstream gatekeeper.yaml and move it to our corresponding files under staticresources/ if it is proper to us.
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.
Hi @yjst2012 it seems straightforward thanks! Just one question before we can get in in.
@@ -41,11 +41,11 @@ const ( | |||
|
|||
defaultManagerRequestsCPU = "100m" | |||
defaultManagerLimitCPU = "1000m" | |||
defaultManagerRequestsMem = "256Mi" | |||
defaultManagerRequestsMem = "512Mi" |
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.
Hi @yjst2012 I am also curious about this. Because it will have impact on a scheduler and the masters are of a fixed size.
Which issue this PR addresses:
Fixes ARO-3058
What this PR does / why we need it:
upgrade gatekeeper version from current 3.10.0 to 3.11.1 which is the latest stable
Test plan for issue:
tested on my local dev env
Is there any documentation that needs to be updated for this PR?
NA