This document shows how to disable bundled ingress for a user cluster in Google Distributed Cloud.
By default, bundled ingress is enabled in user clusters. This means that the
istiod
and istio-ingress
Deployments are running. For more information, see
Ingress components.
If you want to use a full installation of Cloud Service Mesh in a user cluster, you might want to disable bundled ingress. This is because bundled ingress is not needed when Cloud Service Mesh is fully installed, and there are potential conflicts between bundled ingress and Cloud Service Mesh.
Disable bundled ingress for a new cluster
Create a user cluster as described in Create a user cluster.
As you fill in your user cluster configuration file:
- Set
disableBundledIngress
totrue
. - Do not specify a value for
loadBalancer.vips.ingressVIP
.
apiVersion: v1 kind: UserCluster ... disableBundledIngress: true ... loadBalancer: vips: controlPlaneVIP: 172.16.21.30 ingressVIP:
Disable bundled ingress for an existing cluster
In your existing user cluster configuration file:
- Set
disableBundledIngress
totrue
. - Remove the
loadBalancer.vips.ingressVIP
value.
Update the cluster:
gkectl update cluster --kubeconfig ADMIN_CLUSTER_KUBECONFIG --config USER_CLUSTER_CONFIG
Replace the following:
ADMIN_CLUSTER_KUBECONFIG: the path of the admin cluster kubeconfig file
USER_CLUSTER_CONFIG: the path of the user cluster configuration file
Manual load balancing
If your cluster uses manual load balancing and you want to disable bundled ingress, do not specify values for the following fields:
loadBalancer.manualLB.ingressHTTPSNodePort
loadBalancer.manualLB.ingressHTTPNodePort
loadBalancer: Kind: ManaulLB manualLB: ingressHTTPSNodePort: ingressHTTPNodePort: controlPlaneNodePort: 30562
Enable bundled ingress for an existing cluster
If you want to enable bundled ingress for an existing user cluster that has
bundled ingress disabled, edit the user cluster configuration file, and run
gkectl update cluster
.