#1. Lets create a new JWT access token.

export ZEEBE_SECRET=$(kubectl get secret identity-secret-for-components -n $UNAMESPACE -o jsonpath="{.data.zeebe-secret}" | base64 --decode)
curl -X POST "https://${UNAMESPACE}.makelabs.in/auth/realms/camunda-platform/protocol/openid-connect/token" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "grant_type=client_credentials" \
  -d "client_id=zeebe" \
  -d "client_secret=${ZEEBE_SECRET}"
                

Copy

View the token using jwt.io website.
Can you identify the subject (sub) claim in the token?
Specifically, where is this (sub) value coming from?

#2. In the helm install step for Camunda, the release number is sent as a parameter (12.4.0).

Copy

In real-life scenario, if you are given an existing Kubernetes environment, how would you find out the Camunda release number?
Hint: Use Project Lens UI app to look for the deployed helm charts.

#3. Assume that a component (say Connectors Pod) is deleted from the runtime deployment.

Copy

How do you re-deploy the missing "Connectors" component?

#4. The elasticsearch pod running in your respective namespace, is it running on http plaintext port or tls?

Copy

Hint: Use kubectl or Project Lens UI app.