You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per Concourse documentation, certificate propagation is done by default in the BOSH deployment but not in the helm chart. This causes resources to fail if there is an SSL proxy in between them. Additionally, none of the existing chart features are able to support this (see this issue for more detail: #293).
Workaround
The helm chart must include (assuming the worker.certsPath is /etc/ssl/certs):
I think this should be easier to configure in the chart. Perhaps setting a boolean in the worker like worker.enableCertificatePropagation would be easy enough to create the worker.env variable to the value of Values.secrets.certsPath.
The text was updated successfully, but these errors were encountered:
Overview
As per Concourse documentation, certificate propagation is done by default in the BOSH deployment but not in the helm chart. This causes resources to fail if there is an SSL proxy in between them. Additionally, none of the existing chart features are able to support this (see this issue for more detail: #293).
Workaround
The helm chart must include (assuming the
worker.certsPath
is/etc/ssl/certs
):Proposal
I think this should be easier to configure in the chart. Perhaps setting a boolean in the worker like
worker.enableCertificatePropagation
would be easy enough to create theworker.env
variable to the value ofValues.secrets.certsPath
.The text was updated successfully, but these errors were encountered: