Stanislav Egorov 88d676a567 Proxy config for workers/workload
New replacements provide ability to use proxy configuration for worker nodes
and workload deployment.

To use proxy the following env vars should be exported for the session when
running phases: HTTP_PROXY, HTTPS_PROXY and NO_PROXY

Make sure to define all of them, especially NO_PROXY. For example, without
adding cluster IP addresses the deployment will fail.

Change-Id: Id08126f77e0a9da31318f1a239c51a6c78a7c88e
2020-10-26 16:54:30 +00:00

35 lines
1.0 KiB
YAML

# These rules inject env vars into the helm-operator function.
apiVersion: airshipit.org/v1alpha1
kind: ReplacementTransformer
metadata:
name: helm-operator-env-vars-replacements
replacements:
# Replace the proxy vars
- source:
objref:
name: env-vars-catalogue
fieldref: env.HTTP_PROXY
target:
objref:
kind: Deployment
name: helm-operator
fieldrefs: ["spec.template.spec.containers[name=helm-operator].env[name=http_proxy].value%REPLACEMENT_HTTP_PROXY%"]
- source:
objref:
name: env-vars-catalogue
fieldref: env.HTTPS_PROXY
target:
objref:
kind: Deployment
name: helm-operator
fieldrefs: ["spec.template.spec.containers[name=helm-operator].env[name=https_proxy].value%REPLACEMENT_HTTPS_PROXY%"]
- source:
objref:
name: env-vars-catalogue
fieldref: env.NO_PROXY
target:
objref:
kind: Deployment
name: helm-operator
fieldrefs: ["spec.template.spec.containers[name=helm-operator].env[name=no_proxy].value%REPLACEMENT_NO_PROXY%"]