Skip to content

Commit bd79e37

Browse files
authored
fix: clarify custom AMI usage with eksctl (coder#848)
1 parent a11c864 commit bd79e37

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

setup/kubernetes/aws.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -180,14 +180,18 @@ as a workspace deployment option, you'll need to
180180
managedNodeGroups:
181181
- name: coder-node-group
182182
amiFamily: Ubuntu2004
183-
ami: <your Ubuntu 20.04 AMI ID>
183+
# Custom AMIs can be used instead of amiFamily
184+
# ami: <your Ubuntu 20.04 AMI ID>
184185
instanceType: <instance-type>
185186
minSize: 1
186187
mazSize: 2
187188
desiredCapacity: 1
188-
overrideBootstrapCommand: |
189-
#!/bin/bash -xe
190-
sudo /etc/eks/bootstrap.sh --apiserver-endpoint '' --b64-cluster-ca 'LS0tLS1...LS0tCg==' '<cluster-name>'
189+
# Uncomment "overrideBootstrapCommand" if you are using a custom AMI
190+
# and replace YOUR_CLUSTER_CA with "certificate-authority-data" from
191+
# your kubeconfig
192+
# overrideBootstrapCommand: |
193+
# #!/bin/bash -xe
194+
# sudo /etc/eks/bootstrap.sh --apiserver-endpoint '' --b64-cluster-ca 'YOUR_CLUSTER_CA' '<cluster-name>'
191195
```
192196

193197
> [See here for a list of EKS-compatible Ubuntu AMIs](https://cloud-images.ubuntu.com/docs/aws/eks/)

0 commit comments

Comments
 (0)