-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Issues: kubernetes/kops
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
Validate YAML / JSON API values
area/usability
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#2809
opened Jun 24, 2017 by
chrislovecnm
Add support for using cloud-controller-manager (external cloud provider) in kops clusters
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#2778
opened Jun 20, 2017 by
wlan0
We might need to enforce "one version at a time" upgrade
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
#2750
opened Jun 14, 2017 by
justinsb
Update DNS Instructions
area/documentation
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#2464
opened Apr 29, 2017 by
chrislovecnm
document .kops file - does VIPER work
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#2435
opened Apr 26, 2017 by
chrislovecnm
Windows node support
Feature Request
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.
#2422
opened Apr 24, 2017 by
ahasnaini
How to deploy addons when spinning the cluster
area/addon-manager
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#2399
opened Apr 21, 2017 by
dolftax
Is it possible to use an external etcd cluster
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#2216
opened Mar 28, 2017 by
egalano
Request to allow specifying extra routes to add to kops subnets to point to pre-existing VPN gateway
area/networking
Feature Request
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#2214
opened Mar 28, 2017 by
kashook
GCE CNI is not working
area/gce
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#2087
opened Mar 9, 2017 by
chrislovecnm
GCE Error message with statestore
area/gce
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#2082
opened Mar 9, 2017 by
chrislovecnm
kubeadm support for bootstrapping clusters
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#1842
opened Feb 10, 2017 by
krisnova
What is kops missing to support a HIPAA compliant cluster
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
kops -h should show ENV variables
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
Block changing nonMasqueradeCIDR
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
P0
#1738
opened Feb 1, 2017 by
justinsb
Improve ELB healthchecks for API
area/rolling-update
area/security
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
#1647
opened Jan 27, 2017 by
chrislovecnm
Deploy a default StorageClass on all clouds
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#1639
opened Jan 26, 2017 by
jsafrane
Update validation for master instance groups
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#1496
opened Jan 16, 2017 by
justinsb
[Feature] Node Conformance Test
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
Jsonpath support for kops
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#1240
opened Dec 22, 2016 by
chrislovecnm
Fix DNS UX
area/DNS
area/documentation
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
AWS Environmental Variable Documentation
area/documentation
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
Can we kope better with existing VPCs, in terms of assigning subnet CIDRs
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
Previous Next
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.