Amazon EKS Installation
Free-tier clusters still need a no-cost license key unless using AWS Marketplace Metered. Request a free key.
Prerequisites
- Amazon EKS cluster, Kubernetes 1.26+.
kubectlconfigured for the target cluster.helm3.- AWS CLI logged in (for Marketplace methods).
Method 1: AWS Marketplace (Metered)
No license key required. Requires an AWS Marketplace subscription. Billing is metered through AWS Marketplace; charges start only when cluster vCPU exceeds 200.
- Product: Wave Autoscale - Kubernetes AI-Driven Autoscaling (Metered) (opens in a new tab)
- Helm chart: delivered via AWS Marketplace.
- Image registry: AWS Marketplace ECR.
- License: handled by the Marketplace metering product.
values-aws-marketplace-metering.yaml
spec:
# Option A: create a new PVC and specify a StorageClass.
storageClassName: "<STORAGE_CLASS_NAME>"
# Option B: use a pre-existing PVC.
# existingPvcName: "<EXISTING_PVC_NAME>"Install
Subscribe to the Marketplace product above and follow AWS Marketplace's "Continuous Delivery" / "Configure software" flow, which provides the exact helm install command for your subscription. Use the values-*.yaml above.
Method 2: AWS Marketplace (BYOL)
License key required, even for free-tier usage. Request a free key for clusters under 200 vCPUs. For larger clusters, see pricing.
- Product: Wave Autoscale - Kubernetes AI-Driven Autoscaling (BYOL) (opens in a new tab)
- Helm chart: delivered via AWS Marketplace.
- Image registry: AWS Marketplace ECR.
- License: Wave-issued license key set in
license.key.
values-aws-marketplace-byol.yaml
license:
key: "<LICENSE_KEY>"
spec:
# Option A: create a new PVC and specify a StorageClass.
storageClassName: "<STORAGE_CLASS_NAME>"
# Option B: use a pre-existing PVC.
# existingPvcName: "<EXISTING_PVC_NAME>"Install
Subscribe to the BYOL Marketplace product above and follow the Marketplace's installation flow with the values file from this section.
Method 3: GHCR
License key required, even for free-tier usage. Request a free key for clusters under 200 vCPUs.
- Helm chart:
https://release.waveautoscale.io/helm-chart - Image registry:
ghcr.io/stclab-inc/* - Pull secret: GHCR pull secret provided by the Wave team.
values-ghcr.yaml
ghcr:
enabled: true
dockerconfigjson: "<GHCR_PULL_SECRET_DOCKERCONFIGJSON>"
license:
key: "<LICENSE_KEY>"
spec:
# Option A: create a new PVC and specify a StorageClass.
storageClassName: "<STORAGE_CLASS_NAME>"
# Option B: use a pre-existing PVC.
# existingPvcName: "<EXISTING_PVC_NAME>"Install
Replace <CHART_VERSION> with the Wave Autoscale Helm chart version you want.
helm repo add wave-autoscale-helm https://release.waveautoscale.io/helm-chart
helm repo update
helm install wave-autoscale-helm wave-autoscale-helm/wave-autoscale-helm \
-f values-ghcr.yaml \
--version <CHART_VERSION> \
--create-namespace \
-n wave-autoscaleVerify the install
kubectl get pods -n wave-autoscaleOpen the web console with port-forward:
kubectl port-forward -n wave-autoscale svc/wave-autoscale-svc 3025:3025Browse to http://localhost:3025.
Default login: username admin, password waveautoscale. Change these from the web console's user-management UI as soon as you're set up.
Update (GHCR method)
helm repo update
helm upgrade wave-autoscale-helm wave-autoscale-helm/wave-autoscale-helm \
-f values-ghcr.yaml \
--version <CHART_VERSION> \
-n wave-autoscaleFor Marketplace methods, follow the Marketplace's update flow.
Uninstall
helm uninstall wave-autoscale-helm -n wave-autoscalePVC retention: the StatefulSet retention policy keeps PVCs after uninstall. Delete the PVC manually only when stored data is no longer needed.
Next steps
- Important: Before You Begin: runtime behaviors to know.
- Helm Values & Environment Variables: full env vars and Helm values.
- Troubleshooting: common issues.