-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Issues: kubernetes/community
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Tool to generate Kubernetes architecture diagrams with Kubernetes icons set
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
sig/architecture
Categorizes an issue or PR as relevant to SIG Architecture.
#4001
opened Aug 14, 2019 by
mkimuram
Subprojects in sigs.yaml will be instantly out of date
area/github-management
Issues or PRs related to GitHub Management subproject
committee/steering
Denotes an issue or PR intended to be handled by the steering committee.
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
sig/contributor-experience
Categorizes an issue or PR as relevant to SIG Contributor Experience.
Determine canonical list of (run-time) dependencies for Kubernetes
kind/documentation
Categorizes issue or PR as related to documentation.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
sig/architecture
Categorizes an issue or PR as relevant to SIG Architecture.
sig/cluster-lifecycle
Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
sig/release
Categorizes an issue or PR as relevant to SIG Release.
#2234
opened Jun 8, 2018 by
jberkus
Update e2e testing guide
area/contributor-guide
Issues or PRs related to the contributor guide
area/developer-guide
Issues or PRs related to the developer guide
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/bug
Categorizes issue or PR as related to a bug.
kind/documentation
Categorizes issue or PR as related to documentation.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
sig/contributor-experience
Categorizes an issue or PR as relevant to SIG Contributor Experience.
sig/testing
Categorizes an issue or PR as relevant to SIG Testing.
#2759
opened Oct 6, 2018 by
nikhita
Track CVEs for kubernetes dependencies...
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
sig/release
Categorizes an issue or PR as relevant to SIG Release.
sig/security
Categorizes an issue or PR as relevant to SIG Security.
#2992
opened Nov 29, 2018 by
brendandburns
Umbrella issue - API conventions, changes, review guidelines
area/contributor-guide
Issues or PRs related to the contributor guide
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
sig/architecture
Categorizes an issue or PR as relevant to SIG Architecture.
#3211
opened Feb 5, 2019 by
liggitt
18 tasks
Define more roles for SIG network
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
sig/network
Categorizes an issue or PR as relevant to SIG Network.
#3258
opened Feb 15, 2019 by
caseydavenport
reconsider posting CI comments on every test failure
kind/bug
Categorizes issue or PR as related to a bug.
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.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
sig/contributor-experience
Categorizes an issue or PR as relevant to SIG Contributor Experience.
sig/testing
Categorizes an issue or PR as relevant to SIG Testing.
sig/usability
Categorizes an issue or PR as relevant to SIG Usability.
api-conventions.md should explain patchStrategy
kind/documentation
Categorizes issue or PR as related to documentation.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
sig/architecture
Categorizes an issue or PR as relevant to SIG Architecture.
sig/contributor-experience
Categorizes an issue or PR as relevant to SIG Contributor Experience.
Contributing to Kubernetes is harder than it should be and problems have unclear owners
area/contributor-guide
Issues or PRs related to the contributor guide
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
sig/contributor-experience
Categorizes an issue or PR as relevant to SIG Contributor Experience.
Research and document password management for community groups
area/community-management
kind/documentation
Categorizes issue or PR as related to documentation.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
sig/contributor-experience
Categorizes an issue or PR as relevant to SIG Contributor Experience.
sig/release
Categorizes an issue or PR as relevant to SIG Release.
Conformance: Handling optional features
area/conformance
Issues or PRs related to kubernetes conformance tests
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
sig/architecture
Categorizes an issue or PR as relevant to SIG Architecture.
#3997
opened Aug 13, 2019 by
johnbelamaric
Clarify the correct ways to differentiate different behavioral modes of API resources
area/developer-guide
Issues or PRs related to the developer guide
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
sig/architecture
Categorizes an issue or PR as relevant to SIG Architecture.
#859
opened Jul 27, 2017 by
pmorie
Revisiting criteria and process for Alpha/Beta/GA
area/enhancements
Issues or PRs related to the Enhancements subproject
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
sig/architecture
Categorizes an issue or PR as relevant to SIG Architecture.
sig/release
Categorizes an issue or PR as relevant to SIG Release.
#4000
opened Aug 14, 2019 by
johnbelamaric
Prune/shuffle projects under the kubernetes/*org
area/code-organization
Issues or PRs related to kubernetes code organization
area/github-management
Issues or PRs related to GitHub Management subproject
committee/steering
Denotes an issue or PR intended to be handled by the steering committee.
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.
priority/awaiting-more-evidence
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
sig/architecture
Categorizes an issue or PR as relevant to SIG Architecture.
sig/contributor-experience
Categorizes an issue or PR as relevant to SIG Contributor Experience.
#5635
opened Oct 8, 2019 by
timothysc
Improve process for requesting Zoom -> YouTube automation
area/community-management
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
sig/contributor-experience
Categorizes an issue or PR as relevant to SIG Contributor Experience.
process for summit team shadows
area/contributor-summit
Issues or PRs related to all Contributor Summit events
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
sig/contributor-experience
Categorizes an issue or PR as relevant to SIG Contributor Experience.
sig elections process check list/how to
area/elections
Issues or PRs related to community elections
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
sig/contributor-experience
Categorizes an issue or PR as relevant to SIG Contributor Experience.
[Tracking Issue] Developer Guide Audit
area/developer-guide
Issues or PRs related to the developer guide
kind/documentation
Categorizes issue or PR as related to documentation.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
sig/contributor-experience
Categorizes an issue or PR as relevant to SIG Contributor Experience.
[Developer Guide Audit] Scheduling
area/developer-guide
Issues or PRs related to the developer guide
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.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
sig/contributor-experience
Categorizes an issue or PR as relevant to SIG Contributor Experience.
sig/scheduling
Categorizes an issue or PR as relevant to SIG Scheduling.
[Developer Guide Audit] Testing
area/developer-guide
Issues or PRs related to the developer guide
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.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
sig/contributor-experience
Categorizes an issue or PR as relevant to SIG Contributor Experience.
sig/testing
Categorizes an issue or PR as relevant to SIG Testing.
#5239
opened Oct 16, 2020 by
mrbobbytables
Refining the way we communicate deprecations/wide-reaching changes to the project
area/contributor-comms
Issues or PRs related to the upstream marketing team
area/release-team
Issues or PRs related to the release-team subproject
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
sig/contributor-experience
Categorizes an issue or PR as relevant to SIG Contributor Experience.
sig/release
Categorizes an issue or PR as relevant to SIG Release.
Document org-wide process for offtopic troll issue response
area/github-management
Issues or PRs related to GitHub Management subproject
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.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
sig/contributor-experience
Categorizes an issue or PR as relevant to SIG Contributor Experience.
Strategy for handling support requests in k/k
area/github-management
Issues or PRs related to GitHub Management subproject
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
sig/contributor-experience
Categorizes an issue or PR as relevant to SIG Contributor Experience.
Some of the links are not working in sig auth folder
kind/bug
Categorizes issue or PR as related to a bug.
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
#8145
opened Nov 12, 2024 by
AmarNathChary
Previous Next
ProTip!
Updated in the last three days: updated:>2024-11-10.