-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Panic error while trying to mount custom ca cert #315
Comments
Hi @Whisper40 , thanks for reporting this issue, I'm not convinced this issue is related to the new CA Env and Volume, as the file Would you be able to provide (and/or redact where applicable) all the environment variables and/or flags you're passing to version-checker to investigate this further? As for - name: VERSION_CHECKER_SELFHOSTED_CA_PATH_REMOTE
value: "/ca.pem"
image: quay.io/jetstack/version-checker:v0.8.5
...
volumes:
- name: version-checker
secret:
defaultMode: 420
secretName: version-checker
- configMap:
defaultMode: 420
name: ca-pemstore
name: ca-pemstore
...
volumeMounts:
- mountPath: /ca.pem
name: ca-pemstore
subPath: ca.pem |
|
Amazing! Thanks @Whisper40 - Let me try and take a look |
Ah! I see the issue! From the output I can see you're missing some If you add the following, things should start working: - name: VERSION_CHECKER_SELFHOSTED_HOST_REMOTE
value: "https://[REPLACE_WITH_URI_TO_REGISTRY]"
- name: VERSION_CHECKER_SELFHOSTED_INSECURE_REMOTE
value: "true"
- name: VERSION_CHECKER_SELFHOSTED_CA_PATH_REMOTE
value: /ca.pem The following Values are tested here: https://github.com/jetstack/version-checker/blob/main/deploy/charts/version-checker/tests/deployment_test.yaml#L268-L272 |
I can confirm that is fixes this error, maybe it should be handled better to understand what's wrong. |
Amazing that, adding the extra env var's resolved your issue and I agree, we should have something in place which validates/ensures that required fields/values are present... I will keep this issue open for history/context but update/rename. Describe the bug To Reproduce Expected behavior |
Describe the bug
Because the helm chart does not support mounting volumes into pod, i manually added volumemount, and created a configmap with my certificate.
I definied this env :
VERSION_CHECKER_SELFHOSTED_CA_PATH_REMOTE: ca.pem
The deployment is crashing with errors logs :
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The goal is that no tls error appears while connecting to a selfhosted registry
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: