Skip to content

Change in git_config results in inability to use combined ca certs #476

Description

@thelangley

Describe the bug

#457

The change results in different behaviour depending on if you're looking at a native git resource in concourse or a custom script.

Could a variable please be created for opting out and using the original behaviour where custom script/container can use the default store for ca certs?

Reproduction steps

  1. deploy concourse onto k8s, using workerAdditionalCerts, ensure certsPath is set on the workers in the helm chart
  2. configure git resource in concourse pipeline with git_config - name: http.sslCAInfo value: /etc/ssl/certs/worker-additional-certs.pem
  3. Notice Concourse is able to clone the repo nicely
  4. create job with script which uses custom image which cds to repo and git pull. note the error as the path to /etc/ssl/certs/worker-additional-certs.pem is no longer valid as Concourse has expanded all certs into separate files and /etc/ssl/certs/worker-additional-certs.pem no longer exists
    ...

Expected behavior

Concourse can clone repos nicely using specific ca certs
Concourse can also run scripts with custom images for various distros and use the system ca-cert store. not necessarily inheriting from the original resource

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions