Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add extra information in the supported labels and annotations tables #7441

Open
hackeramitkumar opened this issue Oct 21, 2022 · 12 comments · May be fixed by #10425
Open

Add extra information in the supported labels and annotations tables #7441

hackeramitkumar opened this issue Oct 21, 2022 · 12 comments · May be fixed by #10425
Assignees
@hackeramitkumar
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation. priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@hackeramitkumar
Copy link
Member

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
@k8s-ci-robot k8s-ci-robot added kind/documentation Categorizes issue or PR as related to documentation. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 21, 2022
@hackeramitkumar hackeramitkumar changed the title Add extra information in the supported labels and annotations table Add extra information in the supported labels and annotations tables Oct 21, 2022
@fabriziopandini
Copy link
Member

/trige accepted

@hackeramitkumar
Copy link
Member Author

/trige accepted

@hackeramitkumar
Copy link
Member Author

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 5, 2022
@hackeramitkumar
Copy link
Member Author

@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
Copy link
Member

@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
Copy link

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-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. and removed triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Jan 19, 2024
@fabriziopandini
Copy link
Member

/help

@k8s-ci-robot
Copy link
Contributor

@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.

@k8s-ci-robot k8s-ci-robot added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Mar 29, 2024
@fabriziopandini
Copy link
Member

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 29, 2024
@fabriziopandini
Copy link
Member

/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
Copy link
Contributor

@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.

@k8s-ci-robot k8s-ci-robot added priority/backlog Higher priority than priority/awaiting-more-evidence. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. labels Mar 29, 2024
@hackeramitkumar
Copy link
Member Author

/assign

@hackeramitkumar hackeramitkumar linked a pull request Apr 11, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hackeramitkumar hackeramitkumar

Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation. priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
4 participants
@fabriziopandini @k8s-ci-robot @k8s-triage-robot @hackeramitkumar