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

Kubernetes Environment #12

Open
blaubaer opened this issue Aug 27, 2024 · 0 comments
Open

Kubernetes Environment #12

blaubaer opened this issue Aug 27, 2024 · 0 comments
Assignees
Labels
accepted This issue was accepted by the code owners. feature_request New feature or request
Milestone

Comments

@blaubaer
Copy link
Member

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

Similar cases as for the Docker Environment, but plus:

  1. 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).
  2. I want to use ssh -D8080 [email protected] 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.
  3. I want to have the correct tools already available inside the cluster.
  4. I don't want that they're polluted by other users.
  5. 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:

  1. Environment variables
  2. Images
  3. Networks
  4. Commands
  5. Container internal users
@blaubaer blaubaer added the feature_request New feature or request label Aug 27, 2024
@blaubaer blaubaer self-assigned this Aug 27, 2024
@blaubaer blaubaer added the accepted This issue was accepted by the code owners. label Aug 27, 2024
@blaubaer blaubaer added this to the v0.1.4 milestone Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted This issue was accepted by the code owners. feature_request New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant