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

[Feature Request] - kubectl "protocol" #242

Open
knpwrs opened this issue Apr 16, 2024 · 1 comment
Open

[Feature Request] - kubectl "protocol" #242

knpwrs opened this issue Apr 16, 2024 · 1 comment
Assignees
Labels
backlog Implementation/fix not planned yet new feature New feature or request
Milestone

Comments

@knpwrs
Copy link

knpwrs commented Apr 16, 2024

Description

It would be really cool to be able to browse and copy files to/from services running in kubernetes using termscp. I imagine an initial remote screen could be a listing of namespaces, and when you drill in you can see pods or services running in that namespace, and then you can navigate the file system like normal.

Changes

A kubectl "protocol" would need to be added to termscp.

Implementation

You can copy files to and from pods running on kubernetes like such:

kubectl cp --namespace prod ./local/path pod-name:./remote/path

Remote files can be listed like such:

kubectl exec --namespace prod --stdin --tty pod-name -- ls ./remote/path

Namespaces can be listed as such:

kubectl get namespaces

Using these (and other) commands it should be possible to implement a kubectl protocol to be able to browse and copy files to/from services running in kubernetes.

@knpwrs knpwrs added the new feature New feature or request label Apr 16, 2024
@knpwrs
Copy link
Author

knpwrs commented Apr 16, 2024

I currently use navi to do very similar things for my running services, just with fuzzy-finding rather than a TUI: https://github.com/knpwrs/dotfiles/blob/f08642f35fe224949ad0c3a959dbe1d3ec24e6f4/home/config/navi/k8s.cheat

@veeso veeso added this to the 0.14.0 milestone Apr 16, 2024
@veeso veeso added the backlog Implementation/fix not planned yet label Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Implementation/fix not planned yet new feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants