This repository has been archived by the owner on Jun 29, 2022. It is now read-only.
Enable self-hosted kubelet updates by default #110
Assignees
Labels
bug
Something isn't working
Comments
invidian
added a commit
that referenced
this issue
Mar 6, 2020
This commit adds controlplane upgrade functionality to 'cluster install' command. If user runs this command on existing cluster, all controlplane helm releases will be upgraded using charts and values.yaml generated by Terraform. If some of controlplane release has been uninstalled by the user, it will be reinstalled to ensure consitency. The upgrade process is atomic, which means that if something goes wrong (e.g. new pod will not become ready), then the upgrade will be rolled back. The upgrade process is done in order recommended by upstream: https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-component-upgrade-order Currently, 'kubelet' is not being upgraded, because of bug in runc on Flatcar Linux. See #110 for more details. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
Mar 6, 2020
This commit adds controlplane upgrade functionality to 'cluster install' command. If user runs this command on existing cluster, all controlplane helm releases will be upgraded using charts and values.yaml generated by Terraform. If some of controlplane release has been uninstalled by the user, it will be reinstalled to ensure consitency. The upgrade process is atomic, which means that if something goes wrong (e.g. new pod will not become ready), then the upgrade will be rolled back. The upgrade process is done in order recommended by upstream: https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-component-upgrade-order Currently, 'kubelet' is not being upgraded, because of bug in runc on Flatcar Linux. See #110 for more details. For testing, --upgrade-kubelets can be used, but it's experimental and not by default at the moment. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
Mar 6, 2020
This commit adds controlplane upgrade functionality to 'cluster install' command. If user runs this command on existing cluster, all controlplane helm releases will be upgraded using charts and values.yaml generated by Terraform. If some of controlplane release has been uninstalled by the user, it will be reinstalled to ensure consistency. The upgrade process is atomic, which means that if something goes wrong (e.g. new pod will not become ready), then the upgrade will be rolled back. The upgrade process is done in order recommended by upstream: https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-component-upgrade-order Currently, 'kubelet' is not being upgraded, because of bug in runc on Flatcar Linux. See #110 for more details. For testing, --upgrade-kubelets can be used, but it's experimental and not by default at the moment. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
Mar 6, 2020
This commit adds controlplane upgrade functionality to 'cluster install' command. If user runs this command on existing cluster, all controlplane helm releases will be upgraded using charts and values.yaml generated by Terraform. If some of controlplane release has been uninstalled by the user, it will be reinstalled to ensure consistency. The upgrade process is atomic, which means that if something goes wrong (e.g. new pod will not become ready), then the upgrade will be rolled back. The upgrade process is done in order recommended by upstream: https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-component-upgrade-order Currently, 'kubelet' is not being upgraded, because of bug in runc on Flatcar Linux. See #110 for more details. For testing, --upgrade-kubelets can be used, but it's experimental and not by default at the moment. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
Mar 6, 2020
This commit adds controlplane upgrade functionality to 'cluster install' command. If user runs this command on existing cluster, all controlplane helm releases will be upgraded using charts and values.yaml generated by Terraform. If some of controlplane release has been uninstalled by the user, it will be reinstalled to ensure consistency. The upgrade process is atomic, which means that if something goes wrong (e.g. new pod will not become ready), then the upgrade will be rolled back. The upgrade process is done in order recommended by upstream: https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-component-upgrade-order Currently, 'kubelet' is not being upgraded, because of bug in runc on Flatcar Linux. See #110 for more details. For testing, --upgrade-kubelets can be used, but it's experimental and not by default at the moment. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
Mar 6, 2020
This commit adds controlplane upgrade functionality to 'cluster install' command. If user runs this command on existing cluster, all controlplane helm releases will be upgraded using charts and values.yaml generated by Terraform. If some of controlplane release has been uninstalled by the user, it will be reinstalled to ensure consistency. The upgrade process is atomic, which means that if something goes wrong (e.g. new pod will not become ready), then the upgrade will be rolled back. The upgrade process is done in order recommended by upstream: https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-component-upgrade-order Currently, 'kubelet' is not being upgraded, because of bug in runc on Flatcar Linux. See #110 for more details. For testing, --upgrade-kubelets can be used, but it's experimental and not by default at the moment. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
Mar 6, 2020
This commit adds controlplane upgrade functionality to 'cluster install' command. If user runs this command on existing cluster, all controlplane helm releases will be upgraded using charts and values.yaml generated by Terraform. If some of controlplane release has been uninstalled by the user, it will be reinstalled to ensure consistency. The upgrade process is atomic, which means that if something goes wrong (e.g. new pod will not become ready), then the upgrade will be rolled back. The upgrade process is done in order recommended by upstream: https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-component-upgrade-order Currently, 'kubelet' is not being upgraded, because of bug in runc on Flatcar Linux. See #110 for more details. For testing, --upgrade-kubelets can be used, but it's experimental and not by default at the moment. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
Mar 9, 2020
This commit adds controlplane upgrade functionality to 'cluster install' command. If user runs this command on existing cluster, all controlplane helm releases will be upgraded using charts and values.yaml generated by Terraform. If some of controlplane release has been uninstalled by the user, it will be reinstalled to ensure consistency. The upgrade process is atomic, which means that if something goes wrong (e.g. new pod will not become ready), then the upgrade will be rolled back. The upgrade process is done in order recommended by upstream: https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-component-upgrade-order Currently, 'kubelet' is not being upgraded, because of bug in runc on Flatcar Linux. See #110 for more details. For testing, --upgrade-kubelets can be used, but it's experimental and not by default at the moment. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
Mar 10, 2020
This commit adds controlplane upgrade functionality to 'cluster install' command. If user runs this command on existing cluster, all controlplane helm releases will be upgraded using charts and values.yaml generated by Terraform. If some of controlplane release has been uninstalled by the user, it will be reinstalled to ensure consistency. The upgrade process is atomic, which means that if something goes wrong (e.g. new pod will not become ready), then the upgrade will be rolled back. The upgrade process is done in order recommended by upstream: https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-component-upgrade-order Currently, 'kubelet' is not being upgraded, because of bug in runc on Flatcar Linux. See #110 for more details. For testing, --upgrade-kubelets can be used, but it's experimental and not by default at the moment. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
Mar 11, 2020
This commit adds controlplane upgrade functionality to 'cluster install' command. If user runs this command on existing cluster, all controlplane helm releases will be upgraded using charts and values.yaml generated by Terraform. If some of controlplane release has been uninstalled by the user, it will be reinstalled to ensure consistency. The upgrade process is atomic, which means that if something goes wrong (e.g. new pod will not become ready), then the upgrade will be rolled back. The upgrade process is done in order recommended by upstream: https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-component-upgrade-order Currently, 'kubelet' is not being upgraded, because of bug in runc on Flatcar Linux. See #110 for more details. For testing, --upgrade-kubelets can be used, but it's experimental and not by default at the moment. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
Mar 11, 2020
This commit adds controlplane upgrade functionality to 'cluster install' command. If user runs this command on existing cluster, all controlplane helm releases will be upgraded using charts and values.yaml generated by Terraform. If some of controlplane release has been uninstalled by the user, it will be reinstalled to ensure consistency. The upgrade process is atomic, which means that if something goes wrong (e.g. new pod will not become ready), then the upgrade will be rolled back. The upgrade process is done in order recommended by upstream: https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-component-upgrade-order Currently, 'kubelet' is not being upgraded, because of bug in runc on Flatcar Linux. See #110 for more details. For testing, --upgrade-kubelets can be used, but it's experimental and not by default at the moment. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
Mar 11, 2020
This commit adds controlplane upgrade functionality to 'cluster install' command. If user runs this command on existing cluster, all controlplane helm releases will be upgraded using charts and values.yaml generated by Terraform. If some of controlplane release has been uninstalled by the user, it will be reinstalled to ensure consistency. The upgrade process is atomic, which means that if something goes wrong (e.g. new pod will not become ready), then the upgrade will be rolled back. The upgrade process is done in order recommended by upstream: https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-component-upgrade-order Currently, 'kubelet' is not being upgraded, because of bug in runc on Flatcar Linux. See #110 for more details. For testing, --upgrade-kubelets can be used, but it's experimental and not by default at the moment. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
Mar 11, 2020
This commit adds controlplane upgrade functionality to 'cluster install' command. If user runs this command on existing cluster, all controlplane helm releases will be upgraded using charts and values.yaml generated by Terraform. If some of controlplane release has been uninstalled by the user, it will be reinstalled to ensure consistency. The upgrade process is atomic, which means that if something goes wrong (e.g. new pod will not become ready), then the upgrade will be rolled back. The upgrade process is done in order recommended by upstream: https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-component-upgrade-order Currently, 'kubelet' is not being upgraded, because of bug in runc on Flatcar Linux. See #110 for more details. For testing, --upgrade-kubelets can be used, but it's experimental and not by default at the moment. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
Mar 11, 2020
This commit adds controlplane upgrade functionality to 'cluster install' command. If user runs this command on existing cluster, all controlplane helm releases will be upgraded using charts and values.yaml generated by Terraform. If some of controlplane release has been uninstalled by the user, it will be reinstalled to ensure consistency. The upgrade process is atomic, which means that if something goes wrong (e.g. new pod will not become ready), then the upgrade will be rolled back. The upgrade process is done in order recommended by upstream: https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-component-upgrade-order Currently, 'kubelet' is not being upgraded, because of bug in runc on Flatcar Linux. See #110 for more details. For testing, --upgrade-kubelets can be used, but it's experimental and not by default at the moment. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
2 tasks
invidian
added a commit
that referenced
this issue
May 20, 2020
This commit disables self-hosted kubelet tests for picking up correct node labels, as it is flaky because of runc bug in current release of Flatcar stable, which makes kubelet pod to never terminate when the pod is scheduled for removal. Once the fix of runc reaches Flatcar stable, this test should be re-enabled. See also #110 Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
May 20, 2020
This commit disables self-hosted kubelet tests for picking up correct node labels, as it is flaky because of runc bug in current release of Flatcar stable, which makes kubelet pod to never terminate when the pod is scheduled for removal. Once the fix of runc reaches Flatcar stable, this test should be re-enabled. See also #110 Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
May 22, 2020
This commit disables self-hosted kubelet tests for picking up correct node labels, as it is flaky because of runc bug in current release of Flatcar stable, which makes kubelet pod to never terminate when the pod is scheduled for removal. Once the fix of runc reaches Flatcar stable, this test should be re-enabled. See also #110 Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
May 25, 2020
This commit disables self-hosted kubelet tests for picking up correct node labels, as it is flaky because of runc bug in current release of Flatcar stable, which makes kubelet pod to never terminate when the pod is scheduled for removal. Once the fix of runc reaches Flatcar stable, this test should be re-enabled. See also #110 Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
May 25, 2020
This commit disables self-hosted kubelet tests for picking up correct node labels, as it is flaky because of runc bug in current release of Flatcar stable, which makes kubelet pod to never terminate when the pod is scheduled for removal. Once the fix of runc reaches Flatcar stable, this test should be re-enabled. See also #110 Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
May 27, 2020
This commit disables self-hosted kubelet tests for picking up correct node labels, as it is flaky because of runc bug in current release of Flatcar stable, which makes kubelet pod to never terminate when the pod is scheduled for removal. Once the fix of runc reaches Flatcar stable, this test should be re-enabled. See also #110 Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
May 28, 2020
This commit disables self-hosted kubelet tests for picking up correct node labels, as it is flaky because of runc bug in current release of Flatcar stable, which makes kubelet pod to never terminate when the pod is scheduled for removal. Once the fix of runc reaches Flatcar stable, this test should be re-enabled. See also #110 Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
May 28, 2020
This commit disables self-hosted kubelet tests for picking up correct node labels, as it is flaky because of runc bug in current release of Flatcar stable, which makes kubelet pod to never terminate when the pod is scheduled for removal. Once the fix of runc reaches Flatcar stable, this test should be re-enabled. See also #110 Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
May 29, 2020
This commit disables self-hosted kubelet tests for picking up correct node labels, as it is flaky because of runc bug in current release of Flatcar stable, which makes kubelet pod to never terminate when the pod is scheduled for removal. Once the fix of runc reaches Flatcar stable, this test should be re-enabled. See also #110 Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian
added a commit
that referenced
this issue
May 29, 2020
This commit disables self-hosted kubelet tests for picking up correct node labels, as it is flaky because of runc bug in current release of Flatcar stable, which makes kubelet pod to never terminate when the pod is scheduled for removal. Once the fix of runc reaches Flatcar stable, this test should be re-enabled. See also #110 Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
iaguis
changed the title
|
A new Flatcar Stable release with an updated runc is expected next week. |
iaguis
added
proposed/next-sprint
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Self-hosted kubelet updates were disabled because Flatcar Stable is shipping a runc version with a bug that caused updates to be unstable.
When a Flatcar Stable release with a newer runc is out, we should validate it and enable self-hosted kubelet updates by default.
The text was updated successfully, but these errors were encountered: