Skip to content

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
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

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.
#196 opened Jul 22, 2016 by justinsb backlog
AWS Environmental Variable Documentation area/documentation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#1124 opened Dec 11, 2016 by krisnova backlog
Fix DNS UX area/DNS area/documentation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#1228 opened Dec 21, 2016 by justinsb 1.5.1
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
[Feature] Node Conformance Test lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#1319 opened Jan 2, 2017 by vendrov backlog
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
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
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
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
kops -h should show ENV variables lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#1764 opened Feb 2, 2017 by chrislovecnm backlog
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.
#1776 opened Feb 3, 2017 by chrislovecnm backlog
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
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
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
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
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
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
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
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
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
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
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
new FAQ documentation area/documentation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#2867 opened Jul 5, 2017 by chrislovecnm
Document kopeio auth lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#2878 opened Jul 6, 2017 by chrislovecnm
ProTip! Adding no:label will show everything without a label.