As part of the 3.2.0 release, we intended to bump the ZTunnel CRD to v1, but this change has slipped through the cracks, and so 3.2.0 was released with a v1alpha1 ZTunnel CRD. We still want to bump the version of the CRD, but now we need to be a bit more careful with it, as customers might have already deployed v1alpha1 CRD instances.

To properly fix the bug, we should:

• Add v1 version to the ZTunnel CRD, making sure that the controller supports both versions
• Make sure v1 is used as the served/stored version by OLM
• Update our docs to use the v1 CRD in all YAML examples
• Add a release note that explains this to avoid confusion

If we later add fields to the ZTunnel CRD, they will not be back-ported to the v1alpha1 version, and the v1alpha1 version will be removed as part of the 3.3.0 release.