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
Bug 1781707: openshift-sdn, CNO: handle new kubeconfig path #420
Bug 1781707: openshift-sdn, CNO: handle new kubeconfig path #420
Conversation
@squeed: An error was encountered adding this pull request to the external tracker bugs for bug 1781707 on the Bugzilla server at https://bugzilla.redhat.com:
Please contact an administrator to resolve this issue, then request a bug refresh with In response to this:
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. |
/retest |
/lgtm |
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 not very fond of having this defined in multiple places, but gets the job done.
Have you discussed this with whatever team moved the file so they know we're depending on it? |
also maybe a good excuse to switch sdn to using |
/retest Please review the full test history for this PR and help us cut down flakes. |
15 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/hold cancel |
Bah: |
weird, failed with no artifacts. either fluke or we really nuked the cluster. |
OK, now I'm really confused: the CNO is privileged and yet it's still getting permission denied. |
selinux |
Yup, but privileged: true should be sufficient. Bah. |
We can't rely on the nodes having a kubeconfig where we used to expect it. The masters still have it, though, so we can just get it in the CNO and pass it to the SDN in a manifest.
Well, that's never going to pass. Looking at the manifests, the kubeconfig we expect should continue to exist on the masters. So, we can just get it from the CNO to fix the immediate in-the-wild bug. So, undo the changes to the CNO, but still stop the SDN from reading kubeconfig. |
gcp took a nap |
filed SDN-740 to stop reading the kubeconfig. |
still more gcp oddities |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: juanluisvaladas, pecameron, squeed 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 |
/retest Please review the full test history for this PR and help us cut down flakes. |
@squeed: All pull requests linked via external trackers have merged. Bugzilla bug 1781707 has been moved to the MODIFIED state. In response to this:
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. |
/cherrypick release-4.3 |
@juanluisvaladas: new pull request created: #429 In response to this:
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. |
Let's pick this to 4.2 too. |
Before merging? OK |
@juanluisvaladas: #420 failed to apply on top of branch "release-4.2":
In response to this:
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. |
We pull the apiserver url from the kubelet's kubeconfig. This has changed, and can be found in one of two places. Check them both.
Ultimately we need to generate this in a more sustainable way, but this is a good workaround (and easily backportable).