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

Allow a user to attach to an already existing network and/or firewall #2301

Open
1 of 2 tasks
mrsimonemms opened this issue Oct 17, 2024 · 1 comment
Open
1 of 2 tasks
Labels
feature Something new

Comments

@mrsimonemms
Copy link
Contributor

What is your feature idea?

As a user creating a Kubefirst deployment, some users may need to put their management cluster into a pre-existing network. Depending upon the cloud provider, we may also need to configure a pre-existing firewall (some cloud providers put the firewall per network, others need it on each machine).

I can see this being a --network-id and --firewall-id option in the CLI which receives the IDs and then the Terraform templates will get that data rather than creating new resources.

This came from a user in our Slack community

Why is it needed?

Some organisations will need to use a pre-existing network due to internal policies.

Is this missing feature preventing you from using kubefirst?

  • Yes

Code of Conduct

  • I agree to follow this project's Code of Conduct
Copy link

linear bot commented Oct 17, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Something new
Projects
None yet
Development

No branches or pull requests

1 participant