GitHub Label List

We use GitHub labels to perform issue triage, track and report on development progress, plan roadmaps, and automate issue grooming.

To ensure that contributing new issues and PRs remains straight-forward, we would like to keep the labels required for submission to a minimum. The remaining labels will be added either by automation or manual grooming by other contributors and maintainers.

The labels in this list originated within Kubernetes at https://github.com/kubernetes/test-infra/blob/master/label_sync/labels.md.

Labels that apply to issues or PRs

LabelDescriptionAdded By
api-reviewCategorizes an issue or PR as actively needing an API review.Any
area/apiIssues or PRs related to an APIAny
area/blogIssues or PRs related to blog entriesAny
area/build-releaseIssues or PRs related to building and releasingAny
area/component/antctlIssues or PRs releated to the command line interface componentAny
area/component/agentIssues or PRs related to the agent componentAny
area/component/cniIssues or PRs related to the cni componentAny
area/component/controllerIssues or PRs related to the controller componentAny
area/component/octant-pluginIssues or PRs related to the octant-plugin componentAny
area/dependencyIssues or PRs related to dependency changesAny
area/endpoint/identityIssues or PRs related to endpoint identityAny
area/endpoint/selectionIssues or PRs related to endpoint selectionAny
area/endpoint/typeIssues or PRs related to endpoint typeAny
area/ipamIssues or PRs related to IP address management (IPAM)Any
area/interfaceIssues or PRs related to network interfacesAny
area/licensingIssues or PRs related to Antrea licensingAny
area/monitoring/auditingIssues or PRs related to auditingAny
area/monitoring/health-performanceIssues or PRs related to health and performance monitoringAny
area/monitoring/loggingIssues or PRs related to loggingAny
area/monitoring/mirroringIssues or PRs related to mirroringAny
area/monitoring/traffic-analysisIssues or PRs related to traffic analysisAny
area/network-policy/actionIssues or PRs related to network policy actionsAny
area/network-policy/apiIssues or PRs related to the network policy APIAny
area/network-polciy/failsafeIssues or PRs related to network policy failsafesAny
area/network-policy/lifecycleIssues or PRs related to the network policy lifecycleAny
area/network-policy/matchIssues or PRs related to matching packetsAny
area/network-policy/named-setIssues or PRs releatd to network policy named setsAny
area/network-policy/precedenceIssues or PRs related to network policy precedenceAny
area/network-policy/scopeIssues or PRs related to network policy scope (namespace, global, etc.)Any
area/network-policy/stagingIssues or PRs related to staging network policiesAny
area/octantIssues or PRs related to OctantAny
area/opsIssues or PRs related to features which support network operations and troubleshootingAny
area/ops/traceflowIssues or PRs related to the Traceflow featureAny
area/ovs/openflowIssues or PRs related to Open vSwitch Open FlowAny
area/ovs/ovsdbIssues or PRs related to Open vSwitch databaseAny
area/OS/linuxIssues or PRs related to the Linux operating systemAny
area/OS/windowsIssues or PRs related to the Windows operating systemAny
area/provider/awsIssues or PRs related to aws providerAny
area/provider/azureIssues or PRs related to azure providerAny
area/provider/gcpIssues or PRs related to gcp providerAny
area/provider/vmwareIssues or PRs related to vmware providerAny
area/proxyIssues or PRs related to proxy functions in AntreaAny
area/proxy/clusteripIssues or PRs related to the implementation of ClusterIP ServicesAny
area/proxy/nodeportIssues or PRs related to the implementation of NodePort ServicesAny
area/proxy/nodeportlocalIssues or PRs related to the NodePortLocal featureAny
area/security/access-controlIssues or PRs related to access controlAny
area/security/controlplaneIssues or PRs related to controlplane securityAny
area/security/dataplaneIssues or PRs related to dataplane securityAny
area/testIssues or PRs related to unit and integration tests.Any
area/test/communityIssues or PRs related to community testingAny
area/test/e2eIssues or PRs related to Antrea specific end-to-end testing.Any
area/test/infraIssues or PRs related to test infrastructure (Jenkins configuration, Ansible playbook, Kind wrappers, …)Any
area/transit/encapsulationIssues or PRs related to encapsulationAny
area/transit/addressingIssues or PRs related to IP addressing category (unicast, multicast, broadcast, anycast)Any
area/transit/encryptionIssues or PRs related to transit encryption (IPSec, SSL)Any
area/transit/qosIssues or PRs related to transit qos or policingAny
area/transit/routingIssues or PRs related to routing and forwardingAny
kind/api-changeCategorizes issue or PR as related to adding, removing, or otherwise changing an API.Any
kind/bugCategorizes issue or PR as related to a bug.Any
kind/cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debtAny
kind/deprecationCategorizes issue or PR as related to feature marked for deprecationAny
kind/designCategorizes issue or PR as related to designAny
kind/documentationCategorizes issue or PR as related to a documentation.Any
kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing testAny
kind/featureCategorizes issue or PR as related to a new feature.Any
kind/supportCategorizes issue or PR as related to a support question.Any
kind/taskCategorizes issue or PR as related to a routine task that needs to be performed.Any
lifecycle/activeIndicates that an issue or PR is actively being worked on by a contributor.Any
lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Any
lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Any
priority/awaiting-more-evidenceLowest priority. Possibly useful, but not yet enough support to actually get it done.Any
priority/backlogHigher priority than priority/awaiting-more-evidence.Any
priority/critical-urgentHighest priority. Must be actively worked on as someone’s top priority right now.Any
priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Any
priority/import-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Any
ready-to-workIndicates that an issue or PR has been sufficiently triaged and prioritized and is now ready to work.Any
size/LDenotes a PR that changes 100-499 lines, ignoring generated files.Any
size/MDenotes a PR that changes 30-99 lines, ignoring generated files.Any
size/SDenotes a PR that changes 10-29 lines, ignoring generated files.Any
size/XLDenotes a PR that changes 500+ lines, ignoring generated files.Any
size/XSDenotes a PR that changes 0-9 lines, ignoring generated files.Any
triage/duplicateIndicates an issue is a duplicate of other open issue.Humans
triage/needs-informationIndicates an issue needs more information in order to work on it.Humans
triage/not-reproducibleIndicates an issue can not be reproduced as described.Humans
triage/unresolvedIndicates an issue that can not or will not be resolved.Humans

Labels that apply only to issues

LabelDescriptionAdded By
good first issueDenotes an issue ready for a new contributor, according to the “help wanted” guidelines.Anyone
help wantedDenotes an issue that needs help from a contributor. Must meet “help wanted” guidelines.Anyone

Labels that apply only to PRs

LabelDescriptionAdded By
approvedIndicates a PR has been approved by owners in accordance with GOVERNANCE.md guidelines.Maintainers
vmware-cla: noIndicates the PR’s author has not signed the VMware CLAVMware CLA Bot
vmware-cla: yesIndicates the PR’s author has signed the VMware CLAVMware CLA Bot
do-not-merge/holdIndicates a PR should not be merged because someone has issued a /hold commandMerge Bot
do-not-merge/work-in-progressIndicates that a PR should not be merged because it is a work in progress.Merge Bot
lgtmIndicates that a PR is ready to be merged.Merge Bot