GA: Promote Kustomization API to kustomize.toolkit.fluxcd.io/v1

[stefanprodan]

API changes

The Kustomization kind was promoted from v1beta2 to v1 (GA) and deprecated fields were removed.

The kustomizations.source.toolkit.fluxcd.io CRD contains the following versions:

• v1 (storage version)
• v1beta2 (deprecated)
• v1beta1 (deprecated)

Upgrade

The Kustomization v1 API is backwards compatible with v1beta2 with the following exceptions:

• the deprecated field .spec.validation was removed
• the deprecated field .spec.patchesStrategicMerge was removed (replaced by .spec.patches)
• the deprecated field .spec.patchesJson6902 was removed (replaced by .spec.patches)

To upgrade from v1beta2, after deploying the new CRD and controller, set apiVersion: kustomize.toolkit.fluxcd.io/v1 in the YAML files that contain Kustomization definitions and remove the deprecated fields if any. Bumping the API version in manifests can be done gradually. It is advised to not delay this procedure as the beta versions will be removed after 6 months.

Closes: #755
Closes: #664

[hiddeco]

This looks good enough to me to be released.

In terms of the spec doc, I think it could use another proof read to see if more interlinking between sections is possible, and to align tone of voice between different sections. In addition to reducing the usage of "kustomize-controller" as at some point based on the context it can just be called "controller", and other nits like this. But not blocking to move forward, as structure wise it's 💯.

Thanks @stefanprodan and @aryan9600 🙇 🥇

[aryan9600]

I think it could use another proof read to see if more interlinking between sections is possible

i completely agree. one particular instance that comes to mind is how can we make the sops guide and the decryption section more compatible/co-existent?

[hiddeco]

Another thing I ran into is that we first talk about

By default, a Kustomization apply runs under the cluster admin account [...]

but then later have a section on how this default can be changed. I think this should eventually be rewritten in a way which brings the override more to the foreground, as people who read lazily may have had their alarm bells ring before they actually notice this.

[darkowlzz]

Left some suggestions in the API spec doc. There are some references of GitRepository instead of Kustomization which need to be fixed, but the other suggestions can be used or ignored as they may be subjective.

[darkowlzz]

LGTM!

docs index is now fixed