Ingress
By default, the OpenShell gateway is only reachable inside the cluster. To let CLI clients connect without a kubectl port-forward, expose the gateway through an ingress.
OpenShell uses the Kubernetes Gateway API for ingress. The chart creates a GRPCRoute that routes inbound gRPC traffic to the gateway pod. You need a Gateway API implementation installed on your cluster to fulfill the GRPCRoute. This page uses Envoy Gateway, which the chart is tested with.
Install Envoy Gateway
Envoy Gateway installs the Gateway API CRDs and registers the eg GatewayClass:
Verify the GatewayClass is accepted:
The ACCEPTED column should show True.
Install OpenShell with Gateway API enabled
Enable the GRPCRoute and let the chart create a Gateway resource in the openshell namespace:
Get the external address
After the Gateway is provisioned, Envoy Gateway creates a LoadBalancer service in the openshell namespace. Wait for it to get an external address:
Once the EXTERNAL-IP is assigned, register the gateway with the CLI:
Configure SSH relay
For sandbox SSH connections to work through the external address, set server.sshGatewayHost and server.sshGatewayPort to the hostname and port that CLI clients can reach:
Next Steps
Return to Setup to complete the installation.