Skip to content
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

Jump to bottom

Upgrading K8s to v1.12 #183

Closed
tennix opened this issue Nov 19, 2018 · 4 comments · Fixed by #195
Closed

Upgrading K8s to v1.12 #183

tennix opened this issue Nov 19, 2018 · 4 comments · Fixed by #195

Comments

@tennix
Copy link
Member

tennix commented Nov 19, 2018

Kubernetes v1.12 has been released for about 2 months. The local persistent volume scheduling bug #180 has been fixed in v1.12. We should consider upgrading to this version.
@gregwebs
Copy link
Contributor

GCP is only at 1.11.2 right now :(

What does it mean to upgrade to 1.12? Can you list out the new APIs that would be used?

@tennix
Copy link
Member Author

tennix commented Nov 19, 2018

I don't think we'll use any new API when we upgrade our DinD to v1.12. We just want to make sure the scheduling issue #180 won't happen in our DinD testing environment. We can still use v1.10 or later versions.

@gregwebs
Copy link
Contributor

👍

@gregwebs
Copy link
Contributor

I am all for doing anything to make DinD more reliable

@onlymellb onlymellb mentioned this issue Nov 23, 2018
Merged
yahonda pushed a commit that referenced this issue Dec 27, 2021
@ran-huang
en: fix commonName of all certificate (#183)
677b109
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add script to support launch k8s v1.12 onlymellb/tidb-operator
2 participants
@gregwebs @tennix