Skip to main content

Agent Lifecycle and Upgrades

Use this guide to operate an existing DevOps Genie Agent installation.

Check status​

export DG_NAMESPACE=devopsgenie
export DG_RELEASE=dg-agent

kubectl get pods -n "$DG_NAMESPACE" -l app.kubernetes.io/instance="$DG_RELEASE"
kubectl get deploy -n "$DG_NAMESPACE" -l app.kubernetes.io/instance="$DG_RELEASE"

Then open Integrations in DevOps Genie and confirm that the agent is live.

Upgrade​

helm repo update
helm upgrade "$DG_RELEASE" devopsgenie/dg-platform-agent \
  --namespace "$DG_NAMESPACE" \
  -f values.yaml

The controller reconnects after the new pod starts. Capability readiness updates in the product after the agent reconnects and reports its current configuration.

Rotate the API key​

When rotating agent credentials:

  1. Generate or retrieve a new agent API key from DevOps Genie.
  2. Update the Kubernetes Secret that stores DG_API_KEY.
  3. Restart the controller deployment.
  4. Confirm the agent reconnects in Integrations.
  5. Revoke the old key after the new one is active.
kubectl create secret generic dg-platform-agent \
  --namespace "$DG_NAMESPACE" \
  --from-literal=DG_API_KEY="<new-agent-api-key>" \
  --dry-run=client -o yaml | kubectl apply -f -

kubectl rollout restart deployment \
  --namespace "$DG_NAMESPACE" \
  -l app.kubernetes.io/instance="$DG_RELEASE"

Uninstall​

helm uninstall "$DG_RELEASE" --namespace "$DG_NAMESPACE"

Uninstalling stops agent-powered automation. Existing cloud scan data, findings, compliance posture, and conversations remain in DevOps Genie.

Troubleshooting​

See Agent Offline or Not Ready and Helm and Kubernetes Checks.