Labels

Categorizes issue or PR as related to documentation.

Categorizes issue or PR as related to a consistently or frequently failing test.

Categorizes issue or PR as related to a new feature.

Categorizes issue or PR as related to a flaky test.

Categorizes issue or PR as a question.

Categorizes issue or PR as related to a regression from a prior release.

Indicates that a PR is ready to be merged.

Indicates that an issue or PR is actively being worked on by a contributor.

Denotes an issue or PR is blocked.

Indicates that an issue or PR should not be auto-closed due to staleness.

Denotes an issue or PR that has aged beyond stale.

Denotes an issue or PR has remained open with no activity and has become stale.

Indicates a PR that requires an org member to verify it is safe to test.

Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Denotes a PR or issue that needs to be tested before release.

Indicates a non-member PR verified by an org member that is safe to test.

High priority. Should be prioritized for immediate action once current "urgent" tasks are resolved.

Not that important.

Not that urgent, but is important

Highest priority. Must be actively worked on as someone's top priority right now.

Denotes a PR that will be considered when it comes time to generate release notes.

Denotes a PR that introduces potentially breaking changes that require user action.

Denotes a PR that doesn't merit a release note.

Denotes a PR or issue as being assigned to SIG API.

Denotes a PR or issue as being assigned to SIG App Management.

Denotes a PR or issue as being assigned to SIG Cluster Management.

Denotes a PR or issue as being assigned to SIG Community.

Denotes a PR or issue as being assigned to SIG Infra.

Denotes a PR or issue as being assigned to SIG Managed Service.

Denotes a PR or issue as being assigned to SIG Networking.