To avoid redundant resources and potential conflicts when you use a full
installation of [Cloud Service Mesh](https://docs.cloud.google.com/service-mesh/docs/overview.md.txt), you can disable
bundled ingress in Google Distributed Cloud user clusters. Bundled ingress is enabled by
default, which means that the `istiod` and `istio-ingress` Deployments run in
your user clusters. For more information, see
[Ingress components](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/vmware/docs/how-to/create-service-ingress.md.txt#ingress_components).

## Disable bundled ingress for a new cluster

Create a user cluster as described in
[Create a user cluster](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/vmware/docs/how-to/create-user-cluster.md.txt).

As you fill in your user cluster configuration file:

- Set `disableBundledIngress` to `true`.
- 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` to `true`.
- Remove the `loadBalancer.vips.ingressVIP` value.

Update the cluster:

```
gkectl update cluster --kubeconfig ADMIN_CLUSTER_KUBECONFIG --config USER_CLUSTER_CONFIG
```

Replace the following:

- <var translate="no">ADMIN_CLUSTER_KUBECONFIG</var>: the path of the admin cluster kubeconfig
  file

- <var translate="no">USER_CLUSTER_CONFIG</var>: 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: ManualLB
  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`.

## Related documents

- [Overview of load balancing](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/vmware/docs/how-to/setup-load-balance.md.txt)
- [Create a Service and an Ingress](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/vmware/docs/how-to/create-service-ingress.md.txt)