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

docs: Add section regarding c1.medium and m1.small swap provisioning failures. #4858

Merged
merged 2 commits into from
Oct 21, 2023
Merged

docs: Add section regarding c1.medium and m1.small swap provisioning failures. #4858

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7012234
Update troubleshooting.md
mylesw42 Oct 19, 2023
c876e80
Backport the docs update across all versions
jonathan-innis Oct 21, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions website/content/en/preview/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -179,6 +179,17 @@ approach, and now it's much more restrictive.

## Provisioning

### Instances with swap volumes fail to register with control plane
jonathan-innis marked this conversation as resolved.
Show resolved Hide resolved

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.
Expand Down