Skip to main content

​
Steps to validate Helm release

1

Check Helm release status

Confirm that the Helm release deployed successfully:
helm status plerion-collector-manager -n plerion-system
Example output:
NAME: plerion-collector-manager
LAST DEPLOYED: Tue Nov 21 09:18:00 2023
NAMESPACE: plerion-system
STATUS: deployed
REVISION: 1
2

Verify collector manager pods are running

Ensure the pods are in the Running state and not stuck in Pending or CrashLoopBackOff:
kubectl get pods -n plerion-system
Example output:
NAME                                         READY   STATUS    RESTARTS   AGE
plerion-collector-manager-ccbc55c5d-dr27w    1/1     Running   0          10m
plerion-collector-manager-ccbc55c5d-x255n    1/1     Running   0          10m

​
Common issues

  • CrashLoopBackOff: Inspect pod logs for configuration or dependency errors. 
    kubectl logs <pod-name> -n plerion-system
  • Pending: Check node resources and pod scheduling constraints (e.g., CPU/memory, nodeSelector, or taints).
3

Confirm tenant and integration IDs

Verify that the values in the collector manager secret match those shown on the Plerion platform:To view the secret values:
Running this command will display secrets in plain text. Use with caution.
kubectl get secret plerion-collector-manager -n plerion-system \
  -o go-template='{{range $key, $value := .data}}{{printf "%s: %s\n" $key ($value | base64decode )}}{{end}}'
Example output:
INTEGRATION_ID: [redacted]
INTEGRATION_KEY: [redacted]
TENANT_ID: [redacted]
To view the applied configmap:
kubectl get configmap plerion-collector-manager -n plerion-system \\
  -o go-template='{{range $key, $value := .data}}{{printf "%s: %s\\n" $key $value }}{{end}}'
Example output:
APP_URL: https://au.app.plerion.com
CLIENT_BURST: 10
CLIENT_QPS: 5
HEALTH_PROBE_BIND_ADDRESS: :8081
HTTP_MAX_RETRY_ATTEMPTS: 3
HTTP_MAX_RETRY_BACKOFF: 30s
HTTP_MIN_RETRY_BACKOFF: 1s
LEADER_ELECTION: true
METRICS_BIND_ADDRESS: :8080