Role in the deployment¶
Unleash holds the DE's feature toggles, including the maintenance flag that puts
the DE into a read-only banner state. The DE reads it through the Unleash
section of the deployment configuration: base URL, API path, API token, and the
maintenance flag name.
Prerequisites¶
- Unleash database created.
- The
Unleashgroup variables filled in; see cluster resources.
Deploy¶
From the cluster resources checkout, substituting the namespace the DE runs in:
kubectl apply -f resources/deployments/unleash.yml -n <NAMESPACE>
Verify¶
kubectl -n <NAMESPACE> get pods -l app=unleash
kubectl -n <NAMESPACE> logs deploy/unleash --tail=50
Unleash runs its own schema migrations at startup, so the first start after a version bump takes longer than usual. A pod that restarts repeatedly on first boot is normally failing to reach the database.