Skip to main content

Ingress

Supported Configurations
Running the control plane as a container with:

Configure this when you want vCluster to deploy an Ingress resource to expose the virtual cluster's API server at a hostname. The cluster must have an ingress controller running and a LoadBalancer Service.

This feature is not the same as syncing Ingress resources between the host and virtual clusters. See sync.fromHost.ingressClasses and sync.toHost.ingresses.

vCluster uses a default rule, which uses the ingress.host and ingress.pathType configuration. When configure ingress.spec.rules, vCluster ignores ingress.host and ingress.pathType.

Config reference

ingress required object

Ingress defines options for vCluster ingress deployed by Helm.

enabled required boolean false

Enabled defines if the control plane ingress should be enabled

host required string my-host.com

Host is the host where vCluster will be reachable

pathType required string ImplementationSpecific

PathType is the path type of the ingress

spec required object map[tls:[]]

Spec allows you to configure extra ingress options.

annotations required object map[nginx.ingress.kubernetes.io/backend-protocol:HTTPS nginx.ingress.kubernetes.io/ssl-passthrough:true nginx.ingress.kubernetes.io/ssl-redirect:true]

Annotations are extra annotations for this resource.

labels required object {}

Labels are extra labels for this resource.