Description of Operations

The example application uses a broker and client container deployment with volume mount sharing for pods to access the retrieved secrets. This page includes an example of a broker.yml suitable for creation.

Considerations for Sidecars

If the sidecar and broker/controller pods are in the same namespace, no additional actions need to be taken.

If the sidecar and broker/controller pods are in different namespaces, the sidecar needs to know the broker's namespace using the following environment variable in the sidecar configuration.

Broker is in a Different Namespace

# Required if broker is in a different namespace
        - name: BROKER_NAMESPACE
          value: brokernamespace

Specific Namespace Watched by Broker

By default, the broker/controller watches all pods in the cluster; however, the broker can be configured to only watch pods from a specific namespace using the following environment variable in the broker config.

# Optional: Pods Only in this Namespace will be Watched by Broker
        - name: SIDECAR_NAMESPACE
          value: example