Skip to content
Percona Operators Documentation

Rate this page
☆ ☆ ☆ ☆ ☆
Thanks for your feedback
Thank you! The feedback has been submitted.

Get free database assistance or contact our experts for personalized support.

Get help from Percona

Configure environment variables

You can configure environment variables in Percona Operator for MySQL based on Percona Server for MySQL for the following purposes:

  1. Configure Operator environment variables — Control the Operator’s behavior, such as logging, telemetry, and which namespaces the Operator watches. You set these on the Operator Deployment (deploy/operator.yaml or equivalent).
  2. Define environment variables for cluster components — Set variables for database and proxy Pods through the Custom Resource (deploy/cr.yaml): use supported tuning names (for example bootstrap or HAProxy timeouts) or arbitrary custom names, via env / envFrom and optional ConfigMaps or Secrets.

When to use environment variables

Type Use cases
Operator environment variables - Control logging for debugging and log aggregation.
- Manage telemetry.
- Configure the namespaces for the Operator to watch.
Cluster component environment variables - Use documented names to tune bootstrap, HAProxy, Router, Orchestrator, and backups.
- Pass any extra variables your containers need (for example TZ).
- All of this is configured in the Custom Resource, not on the Operator Deployment.

For field-level details, see Custom Resource options.

Last update: April 17, 2026
Created: April 17, 2026