Skip to main content

Configure Agent Secrets in a Docker Compose setup

Configuring platform secrets is a critical step in ensuring the security and integrity of your applications and integrations. Secrets such as API keys, credentials, and tokens must be stored securely to prevent unauthorized access and potential breaches. This guide provides examples and best practices for managing secrets across various tools and platforms using Kubernetes secrets. Follow the instructions below to configure secrets for your environment.

ArgoCD​

To configure secrets for ArgoCD, ensure you have access to the Kubernetes cluster where ArgoCD is installed. Use Kubernetes secrets to store sensitive information such as repository credentials or webhook tokens. Example:

kubectl create secret generic argocd-repo-creds \
  --from-literal=username=<your-username> \
  --from-literal=password=<your-password> \
  -n argocd

Update the ArgoCD configuration to reference the created secret.

PagerDuty​

For PagerDuty integration, create a secret to store the API key. Example:

kubectl create secret generic pagerduty-api-key \
  --from-literal=apiKey=<your-api-key> \
  -n monitoring

Ensure your monitoring tool (e.g., Prometheus or Alertmanager) is configured to use this secret.

Atlassian Jira and Confluence​

Create secrets for Jira and Confluence API tokens or credentials. Example:

kubectl create secret generic jira-confluence-creds \
  --from-literal=username=<your-username> \
  --from-literal=apiToken=<your-api-token> \
  -n atlassian

Update your integration scripts or tools to reference these secrets.

Backstage Installation​

For Backstage, store sensitive information such as database credentials or API keys in Kubernetes secrets. Example:

kubectl create secret generic backstage-db-creds \
  --from-literal=username=<db-username> \
  --from-literal=password=<db-password> \
  -n backstage

Ensure Backstage configuration files reference these secrets.

Webex​

Store Webex integration tokens securely using Kubernetes secrets. Example:

kubectl create secret generic webex-token \
  --from-literal=token=<your-webex-token> \
  -n communication

Update your Webex integration scripts to use this secret.

Slack​

For Slack, store the bot token or webhook URL in a Kubernetes secret. Example:

kubectl create secret generic slack-token \
  --from-literal=token=<your-slack-bot-token> \
  -n communication

Ensure your Slack integration tools reference this secret.

GitHub​

Store GitHub personal access tokens or SSH keys securely. Example:

kubectl create secret generic github-creds \
  --from-literal=token=<your-personal-access-token> \
  --from-file=sshKey=<path-to-ssh-key> \
  -n github

Update your CI/CD pipelines or tools to use these secrets.