Move Field Explanations to Tasks from Reference

[annasong20]

We want to move all involved examples for individual fields in the Reference section into the Tasks section in our internal site. If you feel the examples are really involved, consider the Tutorials section instead. This structural change is to reserve the Reference section for the syntax of Kustomize fields, objects, etc. for easier perusal. An example of Reference section content is #5247. This division reflects the layout of the Kubernetes site.

[annasong20]

/kind documentation
/triage accepted

[ncapps]

Hi @annasong20 , This there an issue to add a specification for each command to the Reference > API > Kustomization File section?

[ncapps]

/assign ncapps

[annasong20]

This there an issue to add a specification for each command to the Reference > API > Kustomization File section?

@ncapps I didn't create one, but you should feel free to! I figured worst case users could download Kustomize and run kustomize --help, which certainly isn't as convenient as good documentation.

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[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

[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