You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a bug in Systemd (>=226, w/ docker configured to use the systemd cgroup driver, and a docker version before 1.12) which causes wrong CPU metrics in cAdvisor and Heapster.
My question is: how can I upgrade CoreOS version without recreating the cluster?
Fair warning, it's a fairly involved process. For each node type (workers, masters/etcd), the steps roughly are:
Bring up additional infrastructure with the new CoreOS version
New infrastructure joins the cluster
Drain connections to the old infrastructure
Confirm old infrastructure is idle and retire
E.g. for workers,
copy ASG/launch configuration of existing workers, change the ami-id to the newer coreos AMI (the one running beta)
bring up a mirror number of worker nodes running the new CoreOS version
confirm they've joined the cluster and are schedulable
drain pods from the old workers
delete the old ASG/launch configuration for the old workers from Terraform manifests, and apply to terminate the nodes and destroy the old worker instructure.
There's a bug in Systemd (>=226, w/ docker configured to use the systemd cgroup driver, and a docker version before 1.12) which causes wrong CPU metrics in cAdvisor and Heapster.
These problems are reported here and here.
As far as I can tell, the bug is fixed in beta channel. My question is: how can I upgrade CoreOS version without recreating the cluster?
cc @yagonobre
The text was updated successfully, but these errors were encountered: