Ingress
Configure this when you want vCluster to deploy an Ingress resource to expose the tenant cluster's API server at a hostname. The cluster must have an ingress controller running and a LoadBalancer Service.
The upstream ingress-nginx project is deprecated. Existing ingress-based configurations continue to work in vCluster v0.35 and vCluster Platform v4.10, but Gateway API is recommended for new endpoint deployments. See Gateway API and Migrate from ingress-nginx to Gateway API.
This feature is not the same as syncing Ingress resources between the control plane cluster and tenant 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 object
Ingress defines options for vCluster ingress deployed by Helm.
ingress object enabled boolean false
Enabled defines if the control plane ingress should be enabled
enabled boolean false host string my-host.com
Host is the host where vCluster will be reachable
host string my-host.com pathType string ImplementationSpecific
PathType is the path type of the ingress
pathType string ImplementationSpecific spec object map[tls:[]]
Spec allows you to configure extra ingress options.
spec object map[tls:[]] annotations 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.
annotations object map[nginx.ingress.kubernetes.io/backend-protocol:HTTPS nginx.ingress.kubernetes.io/ssl-passthrough:true nginx.ingress.kubernetes.io/ssl-redirect:true] labels object {}
Labels are extra labels for this resource.
labels object {}