Skip to content
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

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #18709

/assign sosiouxme

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.
@openshift-ci-robot openshift-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Mar 8, 2018
@sosiouxme
Copy link
Member

/approve
/lgtm
/retest

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 8, 2018
@openshift-ci-robot
Copy link

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 8, 2018
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

2 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@eparis eparis added this to the v3.9 milestone Mar 9, 2018
@eparis
Copy link
Member

eparis commented Mar 9, 2018

/retest
/hold
hold until after 3.9 GA, then anyone may clear it

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 9, 2018
@eparis
Copy link
Member

eparis commented Mar 28, 2018

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 28, 2018
@0xmichalis
Copy link
Contributor

/retest

@openshift-merge-robot openshift-merge-robot merged commit 7b55dfc into openshift:release-3.9 Mar 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants