-
Notifications
You must be signed in to change notification settings - Fork 35
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
AppSec Deployment does not respect .Values.tls.enabled #217
Comments
@timtrense-leadec: Thanks for opening an issue, it is currently awaiting triage. If you haven't already, please provide the following information:
In the meantime, you can:
DetailsI am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the forked project rr404/oss-governance-bot repository. |
@timtrense-leadec: There are no 'kind' label on this issue. You need a 'kind' label to start the triage process.
DetailsI am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the forked project rr404/oss-governance-bot repository. |
/kind bug |
it's correct, I implemented the appsec in the helm chart without the tls for a first iteration. |
Hey @he2ss, thank you for the quick response. I didn't mean to rush you: just good to have the confirmation to have read the code correctly. |
When setting
tls.enabled: true
, the lapi will provide an https endpoint at 8080.If I see it correctly, the deployment of the appsec component does not respect that when constructing the target URL.
Instead,
http://
is hardcoded. Also, no env vars for theCLIENT_CERT_FILE/CLIENT_KEY_FILE/CACERT_FILE
get set.Do I see that correctly that the appsec component currently does not support
tls.enabled
or am I missing something?PS Besides, great work in providing a helm chart for CrowdSec! Really would like to use it, once I can get AppSec up.
The text was updated successfully, but these errors were encountered: