Replies: 1 comment 1 reply
-
For anyone following after, it is fewer commands but slightly more config: #!/usr/bin/env bash
CLUSTER_NAME=${1:-test-cluster}
REGION=${2:-eu-west-2}
cat > /tmp/eksctl-cluster-config.yaml << EOL
---
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig
metadata:
name: ${CLUSTER_NAME}
region: ${REGION}
iam:
withOIDC: true
addons:
- name: aws-ebs-csi-driver
attachPolicyARNs:
- arn:aws:iam::aws:policy/service-role/AmazonEBSCSIDriverPolicy
nodeGroups:
- name: ng-1
instanceType: m5.large
iam:
withAddonPolicies:
ebs: true
EOL
# Create the cluster
eksctl create cluster -f /tmp/eksctl-cluster-config.yaml
# Make gp2 the default storage class
kubectl patch storageclass gp2 -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}' Not sure if the step to make gp2 the default storage class is strictly necessary, it takes soooo long to test I haven't bothered! |
Beta Was this translation helpful? Give feedback.
1 reply
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
-
Hi,
I'm trying to find the very lightest, simplest way to:
The postgresql helm chart creates a persistent volume claim with no storage class:
I'm trying to work out the correct incantations to make eksctl do this. So far I've got to this:
which already feels like about 3 commands too many, but still leaves my claim kicking out this event:
I'm guessing I've missed something obvious, as this seems such a simple use case, so any pointers on what it is would be much appreciated.
Beta Was this translation helpful? Give feedback.
All reactions