Poor explanation of kustomize support for CRDs

[tombentley]

On this page https://kubectl.docs.kubernetes.io/references/kustomize/kustomization/crds/ it says:

The annotations can be put into openAPI definitions are:

• “x-kubernetes-annotation”: ""
• “x-kubernetes-label-selector”: ""
• “x-kubernetes-identity”: ""
• “x-kubernetes-object-ref-api-version”: “v1”,
• “x-kubernetes-object-ref-kind”: “Secret”,
• “x-kubernetes-object-ref-name-key”: “name”,

but it doesn't explain what those annotations are actually used for.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[aredridel]

Yeah, the CRDs bit seems particularly half baked: dumping a CRD object from the API yields a file that when put in the crds: section, fails to parse.

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[aredridel]

/remove-lifecycle rotten