Skip to content

Commit

Permalink
improve doc
Browse files Browse the repository at this point in the history
  • Loading branch information
leiicamundi committed Oct 18, 2024
1 parent 0392eba commit bfeb3eb
Show file tree
Hide file tree
Showing 2 changed files with 21 additions and 2 deletions.
19 changes: 19 additions & 0 deletions docs/self-managed/setup/deploy/amazon/amazon-eks/eks-helm.md
Original file line number Diff line number Diff line change
Expand Up @@ -404,7 +404,11 @@ identity:
Once you've prepared the `values.yml` file, use the `envsubst` command to substitute the environment variables with their actual values. Run the following command:

```bash
# generate the final values
envsubst < values.yml > generated-values.yml

# print the result
cat generated-values.yml
```

Starting from **Camunda 8.6**, you need to store various passwords in a Kubernetes secret, which will be consumed by the Helm chart. Below is an example of how to set up the required secret:
Expand Down Expand Up @@ -440,6 +444,21 @@ This command:
- Substitutes the appropriate version using the `$CAMUNDA_HELM_CHART_VERSION` environment variable.
- Applies the configuration from `generated-values.yml`.

You can track the progress of the installation using the following command:

```bash
watch -n 5 '
kubectl get pods -n camunda --output=wide;
if [ $(kubectl get pods -n camunda --field-selector=status.phase!=Running -o name | wc -l) -eq 0 ] &&
[ $(kubectl get pods -n camunda -o json | jq -r ".items[] | select(.status.containerStatuses[]?.ready == false)" | wc -l) -eq 0 ];
then
echo "All pods are Running and Healthy - Installation completed!";
else
echo "Some pods are not Running or Healthy";
fi
'
```

**Note for domain installation:** the annotation `kubernetes.io/tls-acme=true` will be [interpreted by cert-manager](https://cert-manager.io/docs/usage/ingress/) and automatically results in the creation of the required certificate request, easing the setup.

<details>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -635,6 +635,8 @@ Once the job shows as `Completed`, the OpenSearch domain is configured correctly
kubectl logs job/setup-opensearch-fgac --namespace camunda
```
6. **Cleanup the resources:**
```bash
kubectl delete job setup-opensearch-fgac --namespace camunda
kubectl delete secret setup-os-secret --namespace camunda
Expand All @@ -645,8 +647,6 @@ By running these commands, you will clean up both the job and the secret, ensuri
</TabItem>
</Tabs>
6. **Cleanup the resources:**
## 3. Install Camunda 8 using the Helm chart
Now that you've exported the necessary values, you can proceed with installing Camunda 8 using Helm charts. Follow the guide [Camunda 8 on Kubernetes](./eks-helm.md) for detailed instructions on deploying the platform to your Kubernetes cluster.

0 comments on commit bfeb3eb

Please sign in to comment.