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

Improve error message for service not in default namespace. #5271

Closed
medyagh opened this issue Sep 5, 2019 · 6 comments · Fixed by #5563
Closed

Improve error message for service not in default namespace. #5271

medyagh opened this issue Sep 5, 2019 · 6 comments · Fixed by #5563
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@medyagh
Copy link
Member

medyagh commented Sep 5, 2019

1- create a NodePort service in not default namespace:

$ kubectlget svc -A
NAMESPACE     NAME                    TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                  AGE
default       kubernetes              ClusterIP   10.96.0.1        <none>        443/TCP                  15d
dgeek-v1      dgeek-helm-dgeek-helm   NodePort    10.103.186.237   <none>        80:32316/TCP             3m40s

2- try to open the service url:

$ minikube service dgeek-helm-dgeek-helm

💣  Error opening service
❌  Error: [SERVICE_NOT_FOUND] Could not find finalized endpoint being pointed to by dgeek-helm-dgeek-helm: Temporary Error: Error getting service dgeek-helm-dgeek-helm: services "dgeek-helm-dgeek-helm" not found
Temporary Error: Error getting service dgeek-helm-dgeek-helm: services "dgeek-helm-dgeek-helm" not found
Temporary Error: Error getting service dgeek-helm-dgeek-helm: services "dgeek-helm-dgeek-helm" not found
Temporary Error: Error getting service dgeek-helm-dgeek-helm: services "dgeek-helm-dgeek-helm" not found
💡  Suggestion: Please make sure the service you are looking for is deployed or is in the correct namespace.
⁉️   Related issues:
    ▪ https://github.com/kubernetes/minikube/issues/4599

😿  If the above advice does not help, please let us know: 
👉  https://github.com/kubernetes/minikube/issues/new/choose

the error message is big and suggestion gets over-shaddowed.

I suggest the error message say

service X was not found in default namespace , please try with "minikube service X -n Y"

@medyagh medyagh added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Sep 5, 2019
@tstromberg tstromberg added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Sep 5, 2019
@rbrishabh
Copy link
Contributor

Hey! I would like to take this up!

@josedonizetti
Copy link
Member

@rbrishabh awesome! Let us know if you have any questions. :)

@RA489
Copy link

RA489 commented Sep 11, 2019

@rbrishabh are you still working on this?

@rbrishabh
Copy link
Contributor

Yes! Will submit a PR today! @RA489

@nanikjava
Copy link
Contributor

nanikjava commented Oct 7, 2019

@medyagh can this issue be assigned to me. I've created PR to fix #5563

@nanikjava
Copy link
Contributor

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
7 participants