Add x-kubernetes annotations to Kustomization CRD

[m00nwtchr]

This allows components lists to be merged instead of replaced when applying a strategic merge patch to a flux Kustomization resource, as long as the OpenAPI schema is provided to Kustomize. (The same approach can be applied to other fields and CRDs)

Example:
ks.yaml:

apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
  name: podinfo
  namespace: default
spec:
  interval: 10m
  targetNamespace: default
  components: [ "../original" ]
  sourceRef:
    kind: GitRepository
    name: podinfo
  path: "./kustomize"
  prune: true
  timeout: 1m

kustomization.yaml:

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
  - ks.yaml

openapi:
  path: https://raw.githubusercontent.com/m00nwtchr/flux2-schemas/refs/heads/m00nwtchr-patch-1/_definitions.json
    
patches:
  - target:
      kind: Kustomization
      version: v1
      group: kustomize.toolkit.fluxcd.io
    patch: |-
      apiVersion: kustomize.toolkit.fluxcd.io/v1
      kind: Kustomization
      metadata:
        name: not-used
      spec:
        components:
          - "../patch"

[matheuscscp]

The CRD YAML file is automatically generated by kubebuilder. If these options are not set via kubebuilder they will be overwritten when the file is re-generated.

[m00nwtchr]

Just noticed that this file is auto-generated, I can see how you're supposed to add this info in kubebuilder: https://book.kubebuilder.io/getting-started but not sure when I'll be able to contribute those changes.