-
Bug
-
Resolution: Done
-
Critical
-
Pipelines 1.19.0
Description of problem:
Self signed certificates are no longer respected by the git resolver in 1.19, making resolving remote tasks from private/self-hosted git provider result in a failure to validate the self-signed certificate.
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
- Host gitea at domain which uses a self-signed certificate
- Create a repo in gitea which contains a pipeline yaml file
- In an Openshift cluster, configure the Openshift Proxy to use the self-signed cert following this documentation: https://github.com/openshift/openshift-docs/blob/a8269cf65696fbd08647c8f3b5d065d53a8a1f52/modules/certificate-injection-using-operators.adoc
- Install Openshift Pipelines in the cluster
- Create a PipelineRun which uses the git-resolver to pull the pipeline from gitea
Actual results:
The git-resolver fails because it cannot validate gitea's certificate
Expected results:
The git-resolver succeeds to pull the pipelinerun, validating gitea's certificate using the certificate bundle mounted from the configmap config-trusted-cabundle
Reproducibility (Always/Intermittent/Only Once): Always
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):
*
- clones
-
SRVKP-8204 Git resolver does not respect custom certificates in 1.19
-
- Closed
-
- is depended on by
-
SRVKP-8202 PaC doesn't report invalid PipelineRun YAML syntax error as comment on GitLab
-
- Closed
-
- links to