User will be able to add custom cert at fix path in delegate at: /opt/harness-delegate/ca-bundle/ This path is fixed because we can only add alternate path in custom image and in custom image volume isn't required because certs are baked in. For this approach to work user must add secretName which contains custom certs.
User will be able to add custom cert at fix path in upgrader at: /ca-bundle . For this approach to work user must add secretName which contains custom certs
Changes:
User will be able to add custom cert at fix path in delegate at: /opt/harness-delegate/ca-bundle/ This path is fixed because we can only add alternate path in custom image and in custom image volume isn't required because certs are baked in. For this approach to work user must add secretName which contains custom certs.
User will be able to add custom cert at fix path in upgrader at: /ca-bundle . For this approach to work user must add secretName which contains custom certs
Add support for DESTINATION_CA_PATH to use custom cert in CI pods, CI_MOUNT_VOLUMES are also supported same as https://developer.harness.io/docs/continuous-integration/use-ci/set-up-build-infrastructure/k8s-build-infrastructure/configure-a-kubernetes-build-farm-to-use-self-signed-certificates/
Testing: