Set SSL_CERT_FILE env variable for Knative Serving controller
#9
Conversation
The `SSL_CERT_FILE` environment variable needs to be set to the CA Certificate that the internal OpenShift registry's TLS certificate was signed with. This fixes x509 errors when pulling from the internal registry.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: bbrowning If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@bbrowning: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
Merging |
…restricted security profile (openshift#1284) (openshift#9) * Allow setting seccompProfile to enable using restricted security profile (knative#13401) * fix features cm Co-authored-by: Evan Anderson <evan.k.anderson@gmail.com> Co-authored-by: Evan Anderson <evan.k.anderson@gmail.com>
The
SSL_CERT_FILEenvironment variable needs to be set to the CACertificate that the internal OpenShift registry's TLS certificate was
signed with. This fixes x509 errors when pulling from the internal registry.