-
Notifications
You must be signed in to change notification settings - Fork 197
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 2097696: Call cluster-info with a namespace #3585
Bug 2097696: Call cluster-info with a namespace #3585
Conversation
In some cases, the user does not own the cluster and thus cannot run cluster-info without the scope of a namespace.
how it looked when I ran it locally (on a minikube node): Successfully built cc32c0f82786
Successfully tagged assisted-service-build:latest
python3 ./tools/wait_for_cluster_info.py --namespace "assisted-installer"
2022-03-29 08:17:40.156445 DEBUG - kubectl --namespace assisted-installer cluster-info
Kubernetes control plane is running at https://192.168.76.2:8443
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nmagnezi, osherdp 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 |
Codecov Report
@@ Coverage Diff @@
## master #3585 +/- ##
==========================================
+ Coverage 66.57% 67.48% +0.90%
==========================================
Files 172 176 +4
Lines 24488 26710 +2222
==========================================
+ Hits 16303 18025 +1722
- Misses 6593 6950 +357
- Partials 1592 1735 +143
|
🤦♂️ The |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/override ci/prow/e2e-metal-assisted-kube-api-net-suite |
@osherdp: Overrode contexts on behalf of osherdp: ci/prow/e2e-metal-assisted-kube-api-net-suite 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-required Please review the full test history for this PR and help us cut down flakes. |
4 similar comments
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
@nmagnezi: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
@nmagnezi: All pull requests linked via external trackers have merged: Bugzilla bug 2097696 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. |
In some cases, the user does not own the cluster and thus cannot run cluster-info without the scope of a namespace.
In some cases, the user does not own the cluster and thus cannot run cluster-info without the scope of a namespace.
In some cases, the user does not own the cluster and thus cannot
run cluster-info without the scope of a namespace.
List all the issues related to this PR
What environments does this code impact?
How was this code tested?
Assignees
/cc @osherdp
/cc @omertuc
Checklist
docs
, README, etc)Reviewers Checklist