You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to able to access Kubernetes cluster resources from within the cluster itself. I don't want to use kubectl exec <whatever> anymore to at first go into another container (which I have to know matches the best).
I want to use ssh -D8080 sso@bastion.host to have a local SOCKS5 proxy to access all cluster internal resources directly from my own computer terminal via curl or even with my favorite browser - without forward each target port explicitly with kubectl port-forward.
I want to have the correct tools already available inside the cluster.
I don't want that they're polluted by other users.
I want that this container/POD disposes (cleaned up) if I do not longer need it, automatically.
Describe the solution you'd like
Instead of the currently supported local environment, we should also add a Kubernetes environment which will run every Bifröst's session inside an own Kubernetes POD on a defined target cluster.
It should be possible to use different:
Environment variables
Images
Networks
Commands
Container internal users
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Similar cases as for the Docker Environment, but plus:
kubectl exec <whatever>
anymore to at first go into another container (which I have to know matches the best).ssh -D8080 sso@bastion.host
to have a local SOCKS5 proxy to access all cluster internal resources directly from my own computer terminal viacurl
or even with my favorite browser - without forward each target port explicitly withkubectl port-forward
.Describe the solution you'd like
Instead of the currently supported local environment, we should also add a Kubernetes environment which will run every Bifröst's session inside an own Kubernetes POD on a defined target cluster.
It should be possible to use different:
The text was updated successfully, but these errors were encountered: