-
Notifications
You must be signed in to change notification settings - Fork 79
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
KubernetesAudit not support https! #219
Comments
Hi! What setup are you using? We have it running in prod behind HTTPS and it is working as expected. If you can send me your config, I can take a closer look and reproduce your issue. |
@penetest are you trying to send Kubernetes audit logs to Sematext or some place else? |
@otisg Yes,I want to collect k8s audit logs by LogAgent, But k8s(18.x) audit webhooks need to https server instead of http server. |
What is the HTTP URL you are referring to? Can you paste it here please? |
you can referre to these,and you will find 'The scheme must be “https”; the URL must begin with “https://“.' |
Yeah. But I am asking what URL you are using? Where exactly - to which URL/endpoint - is your Logagent configured to send k8s audit logs? |
@penetest The Kubernetes Audit plugin in Logagent runs a simple Node.js HTTP server that listens on a port.
Does that make sense? Again, can you share your config? If I see it I can give you better instructions. |
Something we can explore in the future is to add support for HTTPS with the built-in |
What you can also do is configure the Kubernetes API Server to send audit logs directly to Sematext Logs. Check out the product announcement here: https://sematext.com/product-updates/#/2020/we-have-a-new-integration-for-kubernetes-audit-logs Also, please check out how to set it up with a Dynamic Backend, and shipping logs directly to Sematext Logs: https://sematext.com/docs/integration/kubernetes-audit-integration/#kubernetes-audit-dynamic-backend |
Did this work for you, @penetest ? |
No description provided.
The text was updated successfully, but these errors were encountered: