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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
13 Open 1,446 Closed
13 Open 1,446 Closed
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
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Bump cilium to 1.17 for kOps 1.33 area/addons area/api area/documentation cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
#17266 opened Feb 19, 2025 by ameukam Loading…
16
WIP: use node-ipam-controller in ipv6 metal tests area/api area/documentation area/kops-controller area/nodeup cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
#16946 opened Nov 13, 2024 by justinsb Loading…
4
(Experimental) bare-metal with IPv6 area/api area/documentation area/kops-controller area/nodeup cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
#16944 opened Nov 11, 2024 by justinsb Loading…
6
Add support for using ECR as pull-through image cache area/addons area/api area/channels area/documentation area/kops-controller area/nodeup area/provider/aws Issues or PRs related to aws provider area/provider/gcp Issues or PRs related to gcp provider area/provider/openstack Issues or PRs related to openstack provider area/provider/scaleway Issues or PRs related to Scaleway provider area/provider/spotinst Issues or PRs related to spotinst provider area/rolling-update cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
#16593 opened May 30, 2024 by rsafonseca Loading…
19
docs(release): add note to 1.22 about the CA CN rename area/documentation cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
#15324 opened Apr 16, 2023 by agilgur5 Loading…
23
Document Route53 and Google DNS troubleshooting area/DNS area/documentation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#3888 opened Nov 17, 2017 by chrislovecnm
6
Document Cluster Startup area/documentation 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.
#3612 opened Oct 12, 2017 by chrislovecnm
5
How to use kops addons area/addon-manager area/documentation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#3554 opened Oct 6, 2017 by glesperance
16
Explicit write permissions required for AWS area/documentation 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.
#3541 opened Oct 5, 2017 by yangyuqian
3
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
8
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
6
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
@justinsb
7
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
6
ProTip! Exclude everything labeled bug with -label:bug.