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

Cannot delete port forwarding created inside k9s #1657

Closed
hholst80 opened this issue Jul 14, 2022 · 14 comments · Fixed by #1668
Closed

Cannot delete port forwarding created inside k9s #1657

hholst80 opened this issue Jul 14, 2022 · 14 comments · Fixed by #1668
Labels
bug Something isn't working question Further information is requested

Comments

@hholst80
Copy link

Screenshot from 2022-07-14 19-22-42

@slimus
Copy link
Collaborator

slimus commented Jul 15, 2022

Hello @hholst80! How did you create PF record with no container inside? I guess it is a main problem here...

@hholst80
Copy link
Author

Obviously there are containers inside the pod. The PF worked just fine too I just could not remove it.

@slimus
Copy link
Collaborator

slimus commented Jul 16, 2022

@hholst80 have you tried the latest k9s version? Could you please share debug logs? k9s info -> Logs

@hholst80
Copy link
Author

❯ k9s version
 ____  __.________       
|    |/ _/   __   \______
|      < \____    /  ___/
|    |  \   /    /\___ \ 
|____|__ \ /____//____  >
        \/            \/ 

Version:    v0.25.21
Commit:     14862f3709dc8dda10f749b6415fce0178111a6d
Date:       2022-06-30T18:05:14Z
5:02PM INF 🐶 K9s starting up...
5:02PM INF ✅ Kubernetes connectivity
5:02PM WRN No context specific skin file found -- /home/om/.config/k9s/local_skin.yml
5:02PM WRN No skin file found -- /home/om/.config/k9s/skin.yml. Loading stock skins.
5:02PM WRN Custom view load failed /home/om/.config/k9s/views.yml error="open /home/om/.config/k9s/views.yml: no such file or directory"
5:02PM WRN CustomView watcher failed error="no such file or directory"
5:02PM WRN unable to resolve ports on default/mongodb-64dcbcf6c8-sbxkz error="no exposed ports"
5:03PM ERR no port-forward defined
5:03PM WRN No custom benchmark config file found
5:03PM WRN No custom benchmark config file found
5:03PM ERR Unable to parse selection default/mongodb-64dcbcf6c8-sbxkz||27017:27017
5:03PM WRN No custom benchmark config file found
5:03PM WRN No custom benchmark config file found
5:03PM WRN No custom benchmark config file found
5:03PM WRN No custom benchmark config file found

@derailed derailed added the question Further information is requested label Jul 17, 2022
@derailed
Copy link
Owner

@hholst80 Could you share pics of how you've created the portforward in the first place? ie the port-forward dialog.
Thank you!

@Elettronik
Copy link

I got the same error:

The port forward was created by specifying only the port in PF dialog

@derailed derailed added the bug Something isn't working label Jul 18, 2022
@slimus
Copy link
Collaborator

slimus commented Jul 19, 2022

Dup #1420?

@hholst80
Copy link
Author

image

@slimus
Copy link
Collaborator

slimus commented Jul 20, 2022

@hholst80 thank you! I've started working on it

@hholst80
Copy link
Author

IDK if it's relevant or not but I typically never defined any container ports neither in Dockerfile nor Pod spec.

@slimus
Copy link
Collaborator

slimus commented Jul 20, 2022

@hholst80 you can try my branch. Thanks a lot!

@hholst80
Copy link
Author

@hholst80 you can try my branch. Thanks a lot!

I'd be happy to. Do you provide automatic builds? Otherwise I'll just wait for the fix to be available in the normal route.

@hholst80
Copy link
Author

hholst80 commented Aug 3, 2022

Works fine now. Thanks guys! (Tested with v0.26.1)

@derailed
Copy link
Owner

derailed commented Aug 3, 2022

@hholst80 WooT!! Thank you for reporting back Henrick!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants