-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Change kube2sky to use token-system-dns secret, point at https endpoint ... #7154
Conversation
1310e8c
to
4828f18
Compare
After I get an LGTM and a clean e2e, I'll rebuild the kube2sky:1.2 image and push before merging. |
source: | ||
secret: | ||
target: | ||
kind: Secret |
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.
@pmorie have we fixed or disproved the Secret idempotency problem?
LGTM but question to @pmorie re: secrets kube2sky needs a near-total overhaul, but that should not stop this PR. |
…nt (instead of kubernetes-ro service).
E2Es are green except the load balancer test (I haven't fetched/rebased since last night when LBs were broken). |
Change kube2sky to use token-system-dns secret, point at https endpoint ...
This merge appears to have significantly increased flakyness of DNS e2e tests (see #7453 for details). Broken cluster DNS in turn causes a few other e2e tests which rely on DNS to fail. I'm going to test that a rollback improves things, and then do it. |
I ran into some problems with the |
...(instead of kubernetes-ro service).