-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[release-3.9] diagnostic reorg and NetworkCheck fix #18903
[release-3.9] diagnostic reorg and NetworkCheck fix #18903
Conversation
Use convenience function that could be refactored to be based on something else, rather than directly depending on docker.
Formerly, in order to run diagnostics inside a pod, NetworkCheck looked up the user's kubeconfig file and wrote it to a secret for the pod to use as its kubeconfig. However, this only worked if the current context is the cluster-admin. Cluster diagnostics can work even if the cluster-admin context is not currently selected. For NetworkCheck to work the same it is now a cluster diagnostic, and it writes a new pod kubeconfig with only the cluster-admin context.
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: openshift-cherrypick-robot, sosiouxme 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. |
2 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 |
/hold cancel |
/retest |
This is an automated cherry-pick of #18709
/assign sosiouxme