Google Distributed Cloud software only for VMware uses bundles to mitigate
issues with slow proxy connections during image downloads. This page describes the
different bundle types, bundle contents, naming conventions, and use cases.

## Bundle types

Google Distributed Cloud software only for VMware offers two types of bundles: regular
bundles and full bundles. These bundles contain the necessary components for your
cluster.

A regular bundle contains metadata and manifests only. A full bundle includes
metadata, OS image OVAs, and container image tarballs.

The following table compares the contents of regular and full bundles.

| Bundle Type | Contents |
|---|---|
| Regular | Metadata and manifests only |
| Full | Metadata, OS image OVAs, and container image tarballs |

## Bundle naming conventions

Bundles follow specific naming conventions. You can identify a full bundle by
the `-full.tgz` suffix in its filename.

For example, a full bundle might have a name similar to
`gke-onprem-vsphere-[VERSION]-full.tgz`.

## Bundle use cases

Choose a bundle type based on your environment and network conditions.

### Regular bundle use cases

Use a regular bundle for standard installations. These installations typically
have high-bandwidth access to Google Cloud.

### Full bundle use cases

Use a full bundle in air-gapped environments or production workstations with
slow proxy connections to Google Cloud.

Full bundles offer several benefits:

- Avoid proxy downtime.
- Eliminate the need to enable or disable a proxy for different production environments.
- Distribute full bundle tarballs to workstations.

You can download a full bundle in an environment without a proxy. Since the full
bundle contains all system images, you can run `gkectl prepare` with the full
bundle in your production workstation without connecting to Google Cloud.

## Version differences and limitations

Bundle contents and compatibility differ by Google Distributed Cloud
version:

- Versions 1.33 and higher: The full bundle includes cgroup v2 images and excludes cgroup v1 images, aligning with the default runtime requirements of newer clusters.
- Versions 1.32 and lower: Full bundles don't contain cgroup v2 images. If you require cgroup v2 on an older version, you must use a regular bundle.

## How bundles work with private registries

You can configure a private registry in your cluster configuration files. If you
configure a private registry in the admin cluster file, all user clusters pull
their workload images from that private registry.

If you don't configure a private registry, system images are pulled from
`gcr.io/gke-on-prem-release` using the component access service account,
`component-access-sa`. For more information about private registries in Google Distributed Cloud software only for VMware, see [Configure a private container registry](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/vmware/docs/how-to/private-registry.md.txt).

When you have a proxy and the network speed to connect to Google Cloud is
slow, you can run `gkectl prepare` without a proxy by using a full bundle. After
preparation, you re-enable the proxy and expect minimum connection to external
networks. This method highly improves security.

## What's next

- To download a bundle, see [Downloads](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/vmware/docs/downloads.md.txt#bundle).
- To configure the bundle path, see the [Admin cluster configuration file](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/vmware/docs/how-to/admin-cluster-configuration-file-latest.md.txt#bundlepath-field).
- To learn more about bypassing external networks, see [Configure a private container registry](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/vmware/docs/how-to/private-registry.md.txt).