Open ysiivan opened 1 month ago
Moved from Serving. CC @knative/func-writers
@ysiivan I've found a solution for myself to this issue. You need to tell your buildpacks where your ca-certificates.crt is. You can do this by setting the buildEnvs in your func.yaml file. Set SSL_CERT_DIR to wherever it is you keep your certificates. If you have the SSL_CERT_DIR env set in your environment already, you can use the below mustache syntax to inject it.
runtime: python
registry: registry.local:5000
created: 2024-08-20T00:47:41.658874026+10:00
build:
builder: pack
buildEnvs:
- name: SSL_CERT_DIR
value: {{ env:SSL_CERT_DIR }}
If this still isn't working for you, you can always place your ca-certificates.crt in your function's working directory and replace {{ env:SSL_CERT_DIR }}
with /workspace
Trying to build a function fails with
tls: failed to verify certificate: x509: certificate signed by unknown authority
I am behind the company's ssl terminating/traffic inspecting appliance and I'm used to having to tweak different systems to set the custom certificates.
The question is - how to do it for
knative
?. I followed this, but it made no difference.Any help?
P.S. Incidentally, the documentation shows creating a secret named
customca
, yet it is referred in the controller's yaml ascustom-certs
.