CONFIGURING CUSTOM ENVIRONMENT VARIABLES

Pulp Operator provide the env_vars field to define custom environment variables for containers.

Info

The following environment variables are managed by Pulp Operator and will be overwritten in case defined as custom env var:

• PULP_GUNICORN_TIMEOUT
• PULP_API_WORKERS
• PULP_CONTENT_WORKERS
• REDIS_SERVICE_HOST
• REDIS_SERVICE_PORT
• REDIS_SERVICE_DB
• REDIS_SERVICE_PASSWORD
• PULP_SIGNING_KEY_FINGERPRINT
• POSTGRES_SERVICE_HOST
• POSTGRES_SERVICE_PORT

For more information about Kubernetes environment variables, check the k8s official documentation:

• Define Dependent Environment Variables
• Define Environment Variables for a Container
• Define container environment variables using Secret data

API DEPLOYMENTS

Example of CR configuration for pulpcore-api containers:

spec:
  api:
    env_vars:
    - name: "<env var name>"
      value: "<env var value>"
    - name: "<env var name>"
      valueFrom:
        secretKeyRef:
          key: <secret key>
          name: <secret name>

WORKER DEPLOYMENTS

Example of CR configuration for pulpcore-worker containers:

spec:
  worker:
    env_vars:
    - name: "<env var name>"
      value: "<env var value>"
    - name: "<env var name>"
      valueFrom:
        secretKeyRef:
          key: <secret key>
          name: <secret name>

CONTENT DEPLOYMENTS

Example of CR configuration for pulpcore-content containers:

spec:
  content:
    env_vars:
    - name: "<env var name>"
      value: "<env var value>"
    - name: "<env var name>"
      valueFrom:
        secretKeyRef:
          key: <secret key>
          name: <secret name>

WEB DEPLOYMENTS

Example of CR configuration for pulpcore-web containers:

spec:
  web:
    env_vars:
    - name: "<env var name>"
      value: "<env var value>"
    - name: "<env var name>"
      valueFrom:
        secretKeyRef:
          key: <secret key>
          name: <secret name>

JOBS

It is also possible to define custom env vars for the containers from AdminPasswordJob, MigrationJob, and SigningJob. For example:

spec:
  admin_password_job:
    container:
      env_vars:
      - name: "<env var name>"
        value: "<env var value>"
  migration_job:
    container:
      env_vars:
      - name: "<env var name>"
        value: "<env var value>"
  signing_job:
    container:
      env_vars:
      - name: "<env var name>"
        value: "<env var value>"