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
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.
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?
Code of Conduct
The text was updated successfully, but these errors were encountered: