Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

Community Issues and discussions

area/dependency

Issues or PRs related to dependency changes.

area/deployment

Issues or PRs related to deployment tooling or infrastructure.

area/documentation

Issues or PRs related to documentation.

area/gateway-api

Issues or PRs related to the Gateway (Gateway API working group) API.

area/gateway-provisioner

Issues or PRs related to the Gateway provisioner

Issues or PRs related to the HTTPProxy API.

Issues or PRs related to the Ingress API.

area/ingressroute

Issues or PRs related to the IngressRoute API.

Issues or PRs related to exposing time series metrics.

area/operational

Issues or PRs about making Contour easier to operate as a production service.

area/service-mesh

Issues or PRs about making Contour interoperate with service meshes. Contour is not a service mesh.

Issues or PRs related to exposing status for APIs.

area/sticky-session

Issues or PRs about Contour's support for sticky sessions.

Issues or PRs related to tests or testing tools.

Issues or PRs related to TLS support.

Issues or PRs related to project tools and automation.

Issues or PRs related to the web site.

blocked/needs-design

Categorizes the issue or PR as blocked because it needs a design document.

blocked/needs-envoy

Categorizes the issue or PR as blocked because it needs changes in Envoy.

blocked/needs-gateway-api

Categorizes the issue or PR as blocked because it needs changes in Gateway API.

blocked/needs-info

Categorizes the issue or PR as blocked because there is insufficient information to advance it.

blocked/needs-product

Categorizes the issue or PR as blocked because it needs a decision from product management.

Blocked waiting on a dependency

Issue to be worked on during ContribFest @ KubeCon EU 2023.

Pull requests that update a dependency file

Don't merge this PR until this label is removed.

Indicates that an issue or PR needs attention from a technical writer or a docs update.

Pull requests that update Go code

good first issue

Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.

Denotes an issue ready for any "Hacktoberfest" contributor.

hacktoberfest-accepted

kind/api-change

Categorizes issue or PR as related to adding, removing, or otherwise changing an API

Categorizes issue or PR as related to a bug.

Categorizes issue or PR as related to cleaning up code, process, or technical debt.

Categorizes issue as a decision to be voted on.

kind/deprecation

Categorizes issue or PR as related to a feature/enhancement marked for deprecation.

Categorizes issue or PR as related to design.

kind/failing-test

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 an issue as a user question.

kind/regression

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

Known issues for release notes

lifecycle/accepted

Denotes an issue that has been triaged and determined to be valid.

lifecycle/frozen

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

lifecycle/investigating

Denotes an issue that is assigned and is being actively investigated by the issue owner.

lifecycle/needs-triage

Indicates that an issue needs to be triaged by a project contributor.

lifecycle/stale

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

Needs additional information

priority/awaiting-more-evidence

Lowest priority. Possibly useful, but not yet enough support to actually get it done.

priority/backlog

Higher priority than priority/awaiting-more-evidence.

priority/critical-urgent

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

priority/important-longterm

Important over the long term, but may not be staffed and/or may need multiple releases to complete.

priority/important-soon

Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

release-note/deprecation

A deprecation or removal that needs about a paragraph of explanation in the release notes.

release-note/docs

A documentation change for the release notes.

release-note/infra

An infrastructure update for the release notes.

release-note/major

A major change that needs more than a paragraph of explanation in the release notes.

release-note/minor

A minor change that needs about a paragraph of explanation in the release notes.

release-note/none-required

Marks a PR as not requiring a release note. Should only be used for very small changes.

release-note/small

A small change that needs one line of explanation in the release notes.

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

release-note-action-required

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

Denotes a PR that changes 100-499 lines, ignoring generated files.

Denotes a PR that changes 30-99 lines, ignoring generated files.

Denotes a PR that changes 10-29 lines, ignoring generated files.

Denotes a PR that changes 500-999 lines, ignoring generated files.

Denotes a PR that changes 0-9 lines, ignoring generated files.

Denotes a PR that changes 1000+ lines, ignoring generated files.

No labels found. Sorry about that.