banzaicloud / kurun Goto Github PK

Is your feature request related to a problem? Please describe.
Currently the inlets image is always pulled directly from Docker hub when running the port-forward command. This prevents any proxy mirrors or even private registries from being used.

Describe the solution you'd like to see
Allowing the image to be overridden with a commandline flag and using it to parameterize the line below, would probably go a very long way. (It would also allow to easily go back and forth on versions of inlets).
https://github.com/banzaicloud/kurun/blob/master/kurun.go#L280

Describe alternatives you've considered
Currently, I'm manually updating the image tag on the deployment after running the port-forward command. This is a little tricky w.r.t. timing and definitely not a desired way of working.

Additional context
N/A

Describe the bug
When running the kurun port-forward ... command the following error is returned:

error: timed out waiting for the condition on deployments/app-kurun
Error: exit status 1

It turns out that the root cause is that ghcr.io/inlets/inlets:3.0.1 became unavailable.

❯ docker pull ghcr.io/inlets/inlets:3.0.1
Error response from daemon: Head https://ghcr.io/v2/inlets/inlets/manifests/3.0.1: unauthorized

This issue was automatically created by Allstar.

Security Policy Violation
Dismiss stale reviews not configured for branch master

This issue will auto resolve when the policy is in compliance.

Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.

Is your feature request related to a problem? Please describe.

It would be handy to have a krew plugin from the port-forward feature.

Describe the solution you'd like to see

krew info forward-port

Describe alternatives you've considered

Additional context

Is your feature request related to a problem? Please describe.

Describe the solution you'd like to see

Describe alternatives you've considered

Additional context

Is your feature request related to a problem? Please describe.
Apparently docker is the hardcoded(?) container engine. I personally prefer podman nowadays and it would be nice if this would together with kurun.

Describe the solution you'd like to see
Support podman, too.

Describe alternatives you've considered
I did not test it, but maybe i can symlink docker to the podman binary. Did not test that yet, though.

How about adding a TLS option to inlets so that you don't have to add ghost tunnel as an extra layer?

It should be relatively straight-forward to listen on a different port, given that you've already mounted the cert as a volume.

Btw inlets has also moved to https://github.com/inlets/inlets and grew a small family:

https://github.com/inlets/inlets-operator - automate inlets client/server for any Service LoadBalancer in K8s
https://github.com/inlets/inletsctl - create exit nodes on public Iaas and inletsctl kfwd

Describe the bug

There is a disabled dependency inlets that prevents installing kurun via Homebrew.

Steps to reproduce the issue:

brew install banzaicloud/tap/kurun
Error: inlets has been disabled because it has a removed upstream repository!

Expected behavior

Screenshots

Additional context