Add extra information in the supported labels and annotations tables

[hackeramitkumar]

Follow up : #7418

Detailed Description
Add two columns in the supported labels and annotations table :

• Object the label/annotation applies to
• Managed by Cluster API or by users

Please also define some consistent sort criteria for both tables.

Anything else you would like to add:

[Miscellaneous information that will assist in solving the issue.]

/kind documentation

[fabriziopandini]

/trige accepted

[hackeramitkumar]

/trige accepted

[hackeramitkumar]

/triage accepted

[hackeramitkumar]

@fabriziopandini Can you suggest me some resources ? Where I can find the following details -
a. Object the label/annotation applies to
b. Managed by Cluster API or by users

[fabriziopandini]

@hackeramitkumar you can try to infer this from label/annotation description or dig into the code.
but it is ok also if you come up with a partial work and then we rally on completing it

[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

[fabriziopandini]

/help

[k8s-ci-robot]

@fabriziopandini:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[fabriziopandini]

/triage accepted

[fabriziopandini]

/triage accepted
/priority backlog

Adding good first issue given that I think that also newcomers can kick off this work in https://cluster-api.sigs.k8s.io/reference/labels_and_annotations by:

• sorting label and annotations in alphabetical order
• add two new columns (Applies to & manage by)

Bonus point if the start compiling the two columns inferring from the label/annotations note (or looking into code)

Maintainers then can step in and rally on the PR for missing values, or eventually defer to a follow up iteration

/good-first-issue

[k8s-ci-robot]

@fabriziopandini:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/triage accepted
/priority backlog

Adding good first issue given that I think that also newcomers can kick off this work in https://cluster-api.sigs.k8s.io/reference/labels_and_annotations by:

• sorting label and annotations in alphabetical order
• add two new columns (Applies to & manage by)

Bonus point if the start compiling the two columns inferring from the label/annotations note (or looking into code)

Maintainers then can step in and rally on the PR for missing values, or eventually defer to a follow up iteration

/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[hackeramitkumar]

/assign