-
Notifications
You must be signed in to change notification settings - Fork 116
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
Fix openshift conformance test #128
Fix openshift conformance test #128
Conversation
For |
7b10bb2
to
9f64903
Compare
Updated to 25% |
@@ -11,6 +11,8 @@ spec: | |||
matchLabels: | |||
app: sriov-network-config-daemon | |||
updateStrategy: | |||
rollingUpdate: | |||
maxUnavailable: 25% |
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.
According to https://kubernetes.io/docs/tasks/manage-daemon/update-daemon-set, the default value is 1 for daemonse.
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.
Thanks for the comments!
Updated.
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.
Hmm, I tried to verify this PR by running the tests. It will fail the test unless this value is set to either 10% or 33%. So neither 25% nor 1 would work.
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.
Should we set it to 33% instead?
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.
Updated to 33%.
9f64903
to
89eabb6
Compare
resources: | ||
requests: | ||
cpu: 100m | ||
memory: 1000Mi |
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.
How did you determine the memory request of 1 GB for this daemonset? Seems a little large.
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.
Good question, I didn't measure how much memory the config daemon would require.
My concern was to not make this smaller enough that would affect current deployment. But I agree that it's a little large.
I will make a change to reduce it to 100Mi.
Thanks @martinkennelly !
89eabb6
to
e3a296a
Compare
Hi @zshi-redhat can you please also add it for the operator under the bundle? |
https://bugzilla.redhat.com/show_bug.cgi?id=1958107 Signed-off-by: Zenghui Shi <[email protected]>
https://bugzilla.redhat.com/show_bug.cgi?id=1960574 Signed-off-by: Zenghui Shi <[email protected]>
c173ca6
to
4293b8c
Compare
Signed-off-by: Zenghui Shi <[email protected]>
Done |
No description provided.