-
Notifications
You must be signed in to change notification settings - Fork 2
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
Upgrade Kubernetes #300
Comments
How it is done in GKE: https://cloud.google.com/container-engine/docs/clusters/upgrade
There doesn't seem to be a tool to do this in AWS, sigh :S |
This is the script used to upgrade gce: https://github.com/kubernetes/kubernetes/blob/master/cluster/gce/upgrade.sh |
This is getting urgent. Kubelet is consuming >70%CPU in all machines |
Let's discuss f2f and decide on the plan. |
Sure let's talk f2f. In a nutshell, the plan is to do the following for dev and prod:
(2) and (3) should happen atomically to avoid:
We should probably have 30min maintenance window or so (@pidster could send an email about it) Also, we should first test that the migration works as expected in the dev environment. For that we can create a user and make sure that everything works before and after the migration. |
We also want to make sure this modifications in |
General tasks:
Current key steps in migration workflow:
|
@tomwilkie nothing needs to be done in CloudFlare for this actually, isn't it? |
This process should be added to the future operations runbook (#266) |
We need to upgrade Kubelet to prevent it's high CPU consumption (see kubernetes/kubernetes#19658). Fixed in in version 1.1.4
We are also experiencing kubernetes/kubernetes#16651 (at least in dev) which should be fixed from v1.2.0-alpha.5
The text was updated successfully, but these errors were encountered: