farmotive/kpoof

Quick k8s port-forward utility

kpoof's Issues

kpoof daemon just stop working sometimes

I can see random connection issues with kpood daemon on my local kuber cluster, without any reasons.. it just stops working so i need to restart it.
any ideas how can i troubleshoot this?

Multiple containers in a single pod concatenate the remote port

Given container foo with PORT: 8080/TCP and container bar with PORT: 11211/TCP kpoof will show the final prompt as Note: *nix ports below 1000 are denied, i.e., use '8080' if the pod is exposing 80 or 443. Local port number? (defaults to 808011211):

Expected result: default to 8080

Show current context and allow to switch with kpoof

Hi,

nice project - works even on Windows 10 Using Windows-Subsystem Linux with Ubuntu from Windows store :)

When working with different clusters (i.e. context) it would be really helpful if kpoof would show the current context (kubectl config get current-context) and it would be nice beeing able event to switch context (kubectl config view -o jsonpath='{.contexts[*].name}').

Best regards and thanks for the great work
Andreas

Allow port selection for local mapping to different port

I had this feature in place, but the API choked on it. Will need to revisit, so that someone can use 8080:8081, for example, if the local :8080 is currently bound.

Allow providing Namespace, Pod-Number and Container-Number as parameter

Hi,

it would be great if one could provide Namespace, Pod-Number and Container-Number (and context, if #16 gets implemented) via command line, like kpoof my-namespace 1 2. This would allow to create some shortcuts for frequently used pods.

Best regards
Andreas

Ensure kpoof can run as daemon

We need the ability to run kpoof as a daemon for support and developer setup tools

Pods with multiple ports may fail with the pre-production release

Need to refactor po_port_sniff to parse multiple exposed ports and serve the result as a list for prompt input, defaulting to first exposed port.

Add kpoof tests file

Tests file should include:

• A connected cluster
• A function for minimal Deployment and Service creation (labeled for easy cleanup)
• Test functions for all known use cases (multi-container pods, ports above and below certain ranges, etc)
• A cleanup function

Create service port-forwarding (enabled from kubernetes version ~1.10)

--port option broken

Problem 1

Unrelated to #10 - this problem exists in the current 2.0.2 release:

$ kpoof -p
Namespace? (default foo):
     1	foo
     2	bar
     3 baz
     4	default
     5	kube-public
     6	kube-system
1
Pod number? (default 1):
     1	foo-drupal-758dfdd65b-bdn8h
     2	foo-mariadb-9f654549d-xk5rn

Remote port number? (default 1):
     1	443
     2	80
2
Local port number? (defaults to 80):

Forwarding from 127.0.0.1:50080 -> 2
Forwarding from [::1]:50080 -> 2
Handling connection for 50080
Handling connection for 50080
E0507 10:23:42.880137   63306 portforward.go:331] an error occurred forwarding 50080 -> 2: error forwarding port 2 to pod cd0d5370129de33e996974d349dd0c27cbf37817911a0b5a4dbbf59a8a7c5037, uid : exit status 1: 2018/05/07 14:23:42 socat[6233] E connect(5, AF=2 127.0.0.1:2, 16): Connection refused
E0507 10:23:42.899045   63306 portforward.go:331] an error occurred forwarding 50080 -> 2: error forwarding port 2 to pod cd0d5370129de33e996974d349dd0c27cbf37817911a0b5a4dbbf59a8a7c5037, uid : exit status 1: 2018/05/07 14:23:42 socat[6232] E connect(5, AF=2 127.0.0.1:2, 16): Connection refused
Handling connection for 50080

Problem 2

There is also now an additional regression in master from #10 that now needs to be fixed for the --port option to even fail as it does above. This new problem is just that the CMD needs to be created as and passed as an array. However, once this is fixed, the above existing issue prevents -p from working.

Use fzf instead of (in addition) to number select.

Contextual namespace from input fails

First of all, kpoof is working in primitive form. Woot!

But only for current namespace, and only with the existing port.

Steps to reproduce:
On the farmotive cluster, kns to a namespace with a mysql or mariadb pod. 365bass or basekamp are good options. Run ./kpoof using enter at the namespace selection, and the correct pod number (2 in both examples). You will have a port-forward instantiated at 3306.
Now ./kpoof again, this time selecting the other namespace.
Expected Result: A successful Port forward.
Actual Result: Pod (Resource) not found => error.