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

Ensure volume expansion is permitted when creating a new AWS cluster #4881

Merged
merged 1 commit into from
Sep 24, 2024
Merged

Ensure volume expansion is permitted when creating a new AWS cluster #4881

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
14 changes: 14 additions & 0 deletions docs/hub-deployment-guide/new-cluster/new-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -679,3 +679,17 @@ kubectl get node
It should show you the provisioned node on the cluster if everything works out ok.
````
`````

## AWS only: Expandable storage class

The default storage class that is created when we deploy a cluster to AWS does permit auto-expansion of persistent volumes.
This can cause problems when we want to expand the size of a disk, say used by Prometheus to store metrics data.
We will therefore patch the default storage class to permite auto-expansion.

```bash
# Gain k8s access to the cluster
deployer use-cluster-credentials $CLUSTER_NAME

# Patch the storage class
kubectl patch storageclass gp2 --patch '{\"allowVolumeExpansion\": true}'
```