diff --git a/website/content/en/docs/troubleshooting.md b/website/content/en/docs/troubleshooting.md index d75b3d527d77..28952034ec9d 100644 --- a/website/content/en/docs/troubleshooting.md +++ b/website/content/en/docs/troubleshooting.md @@ -179,6 +179,17 @@ approach, and now it's much more restrictive. ## Provisioning +### Instances with swap volumes fail to register with control plane + +Some instance types (c1.medium and m1.small) are given limited amount of memory (see [Instance Store swap volumes](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-store-swap-volumes.html)). They are subsequently configured to use a swap volume, which will cause the kubelet to fail on launch. The following error can be seen in the systemd logs: + +```bash +"command failed" err="failed to run Kubelet: running with swap on is not supported, please disable swap!..." +``` + +##### Solutions +Disabling swap will allow kubelet to join the cluster successfully, however users should be mindful of performance, and consider adjusting the Provisioner requirements to use larger instance types. + ### DaemonSets can result in deployment failures For Karpenter versions 0.5.3 and earlier, DaemonSets were not properly considered when provisioning nodes. diff --git a/website/content/en/preview/troubleshooting.md b/website/content/en/preview/troubleshooting.md index bc50aa8693cc..ae3b1f47bf88 100644 --- a/website/content/en/preview/troubleshooting.md +++ b/website/content/en/preview/troubleshooting.md @@ -179,6 +179,17 @@ approach, and now it's much more restrictive. ## Provisioning +### Instances with swap volumes fail to register with control plane + +Some instance types (c1.medium and m1.small) are given limited amount of memory (see [Instance Store swap volumes](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-store-swap-volumes.html)). They are subsequently configured to use a swap volume, which will cause the kubelet to fail on launch. The following error can be seen in the systemd logs: + +```bash +"command failed" err="failed to run Kubelet: running with swap on is not supported, please disable swap!..." +``` + +##### Solutions +Disabling swap will allow kubelet to join the cluster successfully, however users should be mindful of performance, and consider adjusting the Provisioner requirements to use larger instance types. + ### DaemonSets can result in deployment failures For Karpenter versions 0.5.3 and earlier, DaemonSets were not properly considered when provisioning nodes. diff --git a/website/content/en/v0.27/troubleshooting.md b/website/content/en/v0.27/troubleshooting.md index 9b2a09507bb5..81c1b5b0b239 100644 --- a/website/content/en/v0.27/troubleshooting.md +++ b/website/content/en/v0.27/troubleshooting.md @@ -194,6 +194,17 @@ If you see this issue happens while using the`extraObjects` key from the values ## Provisioning +### Instances with swap volumes fail to register with control plane + +Some instance types (c1.medium and m1.small) are given limited amount of memory (see [Instance Store swap volumes](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-store-swap-volumes.html)). They are subsequently configured to use a swap volume, which will cause the kubelet to fail on launch. The following error can be seen in the systemd logs: + +```bash +"command failed" err="failed to run Kubelet: running with swap on is not supported, please disable swap!..." +``` + +##### Solutions +Disabling swap will allow kubelet to join the cluster successfully, however users should be mindful of performance, and consider adjusting the Provisioner requirements to use larger instance types. + ### DaemonSets can result in deployment failures For Karpenter versions 0.5.3 and earlier, DaemonSets were not properly considered when provisioning nodes. diff --git a/website/content/en/v0.28/troubleshooting.md b/website/content/en/v0.28/troubleshooting.md index b4c1a8ef4b60..867a43e8d1fb 100644 --- a/website/content/en/v0.28/troubleshooting.md +++ b/website/content/en/v0.28/troubleshooting.md @@ -179,6 +179,17 @@ approach, and now it's much more restrictive. ## Provisioning +### Instances with swap volumes fail to register with control plane + +Some instance types (c1.medium and m1.small) are given limited amount of memory (see [Instance Store swap volumes](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-store-swap-volumes.html)). They are subsequently configured to use a swap volume, which will cause the kubelet to fail on launch. The following error can be seen in the systemd logs: + +```bash +"command failed" err="failed to run Kubelet: running with swap on is not supported, please disable swap!..." +``` + +##### Solutions +Disabling swap will allow kubelet to join the cluster successfully, however users should be mindful of performance, and consider adjusting the Provisioner requirements to use larger instance types. + ### DaemonSets can result in deployment failures For Karpenter versions 0.5.3 and earlier, DaemonSets were not properly considered when provisioning nodes. diff --git a/website/content/en/v0.29/troubleshooting.md b/website/content/en/v0.29/troubleshooting.md index 6cc1a290b4a9..1bfc0b1a543c 100644 --- a/website/content/en/v0.29/troubleshooting.md +++ b/website/content/en/v0.29/troubleshooting.md @@ -179,6 +179,17 @@ approach, and now it's much more restrictive. ## Provisioning +### Instances with swap volumes fail to register with control plane + +Some instance types (c1.medium and m1.small) are given limited amount of memory (see [Instance Store swap volumes](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-store-swap-volumes.html)). They are subsequently configured to use a swap volume, which will cause the kubelet to fail on launch. The following error can be seen in the systemd logs: + +```bash +"command failed" err="failed to run Kubelet: running with swap on is not supported, please disable swap!..." +``` + +##### Solutions +Disabling swap will allow kubelet to join the cluster successfully, however users should be mindful of performance, and consider adjusting the Provisioner requirements to use larger instance types. + ### DaemonSets can result in deployment failures For Karpenter versions 0.5.3 and earlier, DaemonSets were not properly considered when provisioning nodes. diff --git a/website/content/en/v0.30/troubleshooting.md b/website/content/en/v0.30/troubleshooting.md index d75b3d527d77..28952034ec9d 100644 --- a/website/content/en/v0.30/troubleshooting.md +++ b/website/content/en/v0.30/troubleshooting.md @@ -179,6 +179,17 @@ approach, and now it's much more restrictive. ## Provisioning +### Instances with swap volumes fail to register with control plane + +Some instance types (c1.medium and m1.small) are given limited amount of memory (see [Instance Store swap volumes](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-store-swap-volumes.html)). They are subsequently configured to use a swap volume, which will cause the kubelet to fail on launch. The following error can be seen in the systemd logs: + +```bash +"command failed" err="failed to run Kubelet: running with swap on is not supported, please disable swap!..." +``` + +##### Solutions +Disabling swap will allow kubelet to join the cluster successfully, however users should be mindful of performance, and consider adjusting the Provisioner requirements to use larger instance types. + ### DaemonSets can result in deployment failures For Karpenter versions 0.5.3 and earlier, DaemonSets were not properly considered when provisioning nodes. diff --git a/website/content/en/v0.31/troubleshooting.md b/website/content/en/v0.31/troubleshooting.md index d75b3d527d77..28952034ec9d 100644 --- a/website/content/en/v0.31/troubleshooting.md +++ b/website/content/en/v0.31/troubleshooting.md @@ -179,6 +179,17 @@ approach, and now it's much more restrictive. ## Provisioning +### Instances with swap volumes fail to register with control plane + +Some instance types (c1.medium and m1.small) are given limited amount of memory (see [Instance Store swap volumes](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-store-swap-volumes.html)). They are subsequently configured to use a swap volume, which will cause the kubelet to fail on launch. The following error can be seen in the systemd logs: + +```bash +"command failed" err="failed to run Kubelet: running with swap on is not supported, please disable swap!..." +``` + +##### Solutions +Disabling swap will allow kubelet to join the cluster successfully, however users should be mindful of performance, and consider adjusting the Provisioner requirements to use larger instance types. + ### DaemonSets can result in deployment failures For Karpenter versions 0.5.3 and earlier, DaemonSets were not properly considered when provisioning nodes.