-
Notifications
You must be signed in to change notification settings - Fork 40.9k
Fix namespace not found #132856
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
base: master
Are you sure you want to change the base?
Fix namespace not found #132856
Conversation
Welcome @virsuryaircas! |
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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-sigs/prow repository. |
Hi @virsuryaircas. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: virsuryaircas The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind bug
What this PR does / why we need it:
This PR fixes a misleading message in
kubectl get
when the specified namespace does not exist.Previously, it would say:
No resources found in <namespace> namespace
,even if the namespace didn’t exist.
With this change, it now correctly returns:
Error from server (NotFound): namespaces "<name>" not found
.This improves clarity and avoids confusion for users.
Which issue(s) this PR is related to:
N/A – no GitHub issue, submitted directly
Special notes for your reviewer:
This is a user-facing UX improvement for kubectl to handle invalid namespace input more transparently.
Does this PR introduce a user-facing change?
Terminal Output for your ref:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: