This is a cache of https://docs.okd.io/4.15/networking/external_dns_operator/nw-configuring-cluster-wide-egress-proxy.html. It is a snapshot of the page at 2024-11-16T20:33:16.069+0000.
Configuring the cluster-wide proxy on the External <strong>dns</strong> Operator - External <strong>dns</strong> Operator | Networking | OKD 4.15
  1. Documentation
×

Configuring the cluster-wide proxy on the External dns Operator

After configuring the cluster-wide proxy, the Operator Lifecycle Manager (OLM) triggers automatic updates to all of the deployed Operators with the new contents of the HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variables.

Trusting the certificate authority of the cluster-wide proxy

You can configure the External dns Operator to trust the certificate authority of the cluster-wide proxy.

Procedure

  1. Create the config map to contain the CA bundle in the external-dns-operator namespace by running the following command:

    $ oc -n external-dns-operator create configmap trusted-ca

  2. To inject the trusted CA bundle into the config map, add the config.openshift.io/inject-trusted-cabundle=true label to the config map by running the following command:

    $ oc -n external-dns-operator label cm trusted-ca config.openshift.io/inject-trusted-cabundle=true

  3. Update the subscription of the External dns Operator by running the following command:

    $ oc -n external-dns-operator patch subscription external-dns-operator --type='json' -p='[{"op": "add", "path": "/spec/config", "value":{"env":[{"name":"TRUSTED_CA_CONFIGMAP_NAME","value":"trusted-ca"}]}}]'
Verification

  • After the deployment of the External dns Operator is completed, verify that the trusted CA environment variable is added to the external-dns-operator deployment by running the following command:

    $ oc -n external-dns-operator exec deploy/external-dns-operator -c external-dns-operator -- printenv TRUSTED_CA_CONFIGMAP_NAME
    Example output
    trusted-ca