The Wayback Machine - https://web.archive.org/web/20230715023318/https://github.com/kubernetes/kubernetes/contribute
Skip to content

Contribute to kubernetes/kubernetes

Make your first contribution to this repository by tackling one of the issues listed below.

Each issue displayed here is a "good first issue," selected for its relative approachability for first-time contributors.

Good first issues

controller_util_test.go does not follow similar patterns as other unit tests in the repo. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/feature Categorizes issue or PR as related to a new feature. sig/apps Categorizes an issue or PR as relevant to SIG Apps. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
#119133 opened Jul 6, 2023 by kannon92
17
PodGC unit tests do not actually test addition of any conditions. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/feature Categorizes issue or PR as related to a new feature. sig/apps Categorizes an issue or PR as relevant to SIG Apps. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
#118826 opened Jun 23, 2023 by kannon92
11
[FG:InPlacePodVerticalScaling] Implement version skew handling for in-place pod resize sig/node Categorizes an issue or PR as relevant to SIG Node. kind/feature Categorizes issue or PR as related to a new feature. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
#117767 opened May 3, 2023 by vinaykul
29
Report event for the cases when probe returned Unknown result priority/backlog Higher priority than priority/awaiting-more-evidence. sig/node Categorizes an issue or PR as relevant to SIG Node. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
#116026 opened Feb 24, 2023 by SergeyKanzhelev
17
Give an indication in container events for probe failure as to whether the failure was ignored due to FailureThreshold priority/backlog Higher priority than priority/awaiting-more-evidence. kind/documentation Categorizes issue or PR as related to documentation. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. sig/node Categorizes an issue or PR as relevant to SIG Node. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. triage/accepted Indicates an issue or PR is ready to be actively worked on.
#115823 opened Feb 16, 2023 by intUnderflow
10
Write the stress test for gRPC, http, and tcp probes priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. sig/node Categorizes an issue or PR as relevant to SIG Node. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
#115782 opened Feb 15, 2023 by SergeyKanzhelev
12
NetworkPolicy tests for blocking north/south traffic priority/backlog Higher priority than priority/awaiting-more-evidence. sig/network Categorizes an issue or PR as relevant to SIG Network. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. triage/accepted Indicates an issue or PR is ready to be actively worked on. area/network-policy Issues or PRs related to Network Policy subproject
#114369 opened Dec 8, 2022 by danwinship
20
Remove dependency on github.com/pkg/errors kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. area/code-organization Issues or PRs related to kubernetes code organization needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
#113627 opened Nov 4, 2022 by alculquicondor
33
Node lifecycle controller does not `markPodsNotReady` when the node `Ready` state changes from `false` to `unknown` kind/bug Categorizes issue or PR as related to a bug. sig/node Categorizes an issue or PR as relevant to SIG Node. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. triage/accepted Indicates an issue or PR is ready to be actively worked on.
#112733 opened Sep 26, 2022 by xenv
17
Incorrect error message for pod thresholds in e2e tests in wait.go kind/flake Categorizes issue or PR as related to a flaky test. sig/windows Categorizes an issue or PR as relevant to SIG Windows. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. sig/testing Categorizes an issue or PR as relevant to SIG Testing. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
#111092 opened Jul 12, 2022 by jayunit100
19
[FG:InPlacePodVerticalScaling] Add E2E test case to revert resource resize patch sig/node Categorizes an issue or PR as relevant to SIG Node. kind/feature Categorizes issue or PR as related to a new feature. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
#109905 opened May 9, 2022 by vinaykul
15
TOB-K8S-004: Pervasive world-accessible file permissions kind/bug Categorizes issue or PR as related to a bug. area/security sig/storage Categorizes an issue or PR as relevant to SIG Storage. sig/node Categorizes an issue or PR as relevant to SIG Node. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. wg/security-audit Categorizes an issue or PR as relevant to WG Security Audit. triage/accepted Indicates an issue or PR is ready to be actively worked on.
#81116 opened Aug 8, 2019 by cji
27
`failed to garbage collect required amount of images. Wanted to free 473842483 bytes, but freed 0 bytes` kind/bug Categorizes issue or PR as related to a bug. sig/node Categorizes an issue or PR as relevant to SIG Node. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. triage/accepted Indicates an issue or PR is ready to be actively worked on.
#71869 opened Dec 8, 2018 by samuela
63
Figure out a way to manage the discrepancy on windows nodes from the linux node kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/windows Categorizes an issue or PR as relevant to SIG Windows. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. triage/accepted Indicates an issue or PR is ready to be actively worked on.
#60338 opened Feb 24, 2018 by dchen1107
20
Move selector immutability check to validation after v1beta1 retires kind/bug Categorizes issue or PR as related to a bug. sig/apps Categorizes an issue or PR as relevant to SIG Apps. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
#50791 opened Aug 16, 2017 by crimsonfaith91
10