-
Notifications
You must be signed in to change notification settings - Fork 297
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
Ingress Upgrade Testing #546
Conversation
Hi @agau4779. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign @rramkumar1 |
8caab2d
to
d9fb8ae
Compare
/assign bowei |
pkg/e2e/status.go
Outdated
) | ||
|
||
const ( | ||
configMapName = "status-cm" |
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 create unique config maps for each run (per framework instance) to avoid potential clashes if we have a messed up run?
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.
hm, on the guitar test side we need to know the name of the configmap in order to check the conents. @rramkumar1 - thoughts? What does a messed-up run look like in this case?
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.
@bowei What do you mean by messed up run?
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.
ignore my comment, after discussion, I don't think it makes sense.
/ok-to-test |
d9fb8ae
to
445739a
Compare
bc5a761
to
5b014bd
Compare
// Loop until we successfully update the config map | ||
for { | ||
var err error | ||
sm.cm, err = sm.f.Clientset.Core().ConfigMaps("default").Update(sm.cm) |
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.
could it a race if we do update rather than patch?
5b014bd
to
6587a75
Compare
options := &e2e.WaitForIngressOptions{ | ||
ExpectUnreachable: runs == 0, | ||
} | ||
ing, err := e2e.WaitForIngress(s, tc.ing, options) |
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 forget -- does this have some delay in the check to avoid excessively spamming when the LB is down?
needUpdate := true | ||
// Framework.shutdown() kills this loop. | ||
for { | ||
if s.MasterUpgraded() && needUpdate { |
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 this in a follow on--
is it possible to separate out the wait for upgrade logic so it's easier to reuse?
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: agau4779, bowei 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 |
Continuation of #392 .