-
Notifications
You must be signed in to change notification settings - Fork 118
Issues: kubernetes/cloud-provider
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
CCM may not work when Instances or InstancesV2 isn't implemented
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
#72
opened Jul 22, 2024 by
xagent003
Standardize the Cloud Controller Manager Build/Release Process
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.
P1
Priority 1
cloud-controller-manager should be able to ignore nodes
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
P2
Priority 2
Remove unecessary flags in cloud-controller-manager
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
P2
Priority 2
Track underlying cloud resources for Services
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
P2
Priority 2
Decoupling Cloud Providers from Kubernetes e2e testing framework
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
P2
Priority 2
API Server Network Proxy: GA
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
P0
Priority 0
Investigate API throttling in routes API calls
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.
P3
Priority 3
Investigate API Throttling in Node Controller
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.
P3
Priority 3
Extracting/Migrating the Credential Provider: KEP + Alpha Implementation
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
P0
Priority 0
kube-controller-manager -> cloud-controller-manager HA migration: KEP + alpha implementation
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
P0
Priority 0
ProTip!
Mix and match filters to narrow down what you’re looking for.