Establishing a Gefyra connection is cumbersome in private K8s clusters, which do not expose a Kubernetes API directly to the developer. A special tunnel for the K8s API access must be established in order to connect.
Allowing Gefyra clients to activate directly upon creation (given an IP range for the client network is specified) would allow clients to connect directly to the Gefyra cluster without having to activate the client first and negotiate the IP range.
Once Gefyra is connected, Cargo can also proxy the Kubernetes API to the developer via the cluster on a certain local port. That would eliminate the need for the step-one tunnel connection entirely.
Why would such a feature be important to you?
It improves the developer's experience with Gefyra as I can connect and run w/o having the K8s API available.
What is the new feature about?
Establishing a Gefyra connection is cumbersome in private K8s clusters, which do not expose a Kubernetes API directly to the developer. A special tunnel for the K8s API access must be established in order to connect. Allowing Gefyra clients to activate directly upon creation (given an IP range for the client network is specified) would allow clients to connect directly to the Gefyra cluster without having to activate the client first and negotiate the IP range.
Once Gefyra is connected, Cargo can also proxy the Kubernetes API to the developer via the cluster on a certain local port. That would eliminate the need for the step-one tunnel connection entirely.
Why would such a feature be important to you?
It improves the developer's experience with Gefyra as I can
connectandrunw/o having the K8s API available.Anything else we need to know?
No response