-
Notifications
You must be signed in to change notification settings - Fork 728
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
support HTTPS certificate-based authentication with k8s API server #513
Comments
Supported in Sysdig Cloud only. There are no immediate plans for support in open source version. |
Should be fixed with 0.7.0. Refer to release notes and to |
Nice, thanks! I'll try it out! |
FYI, I couldn't get this to work, but I think I have an incorrect core assuption. Can I use csysdig to monitor my (remote) kubernetes cluster? The client seems to expect that I'm running sysdig locally. It always wants to access the local file |
At the moment, you can't use csysdig/sysdig to monitor a remote Kubernetes cluster. You will just be able to monitor the local Kubernetes node where your instance is running. The connection to the Kubernetes API server is done in order to fetch metadata information about your local containers (pods, labels, controllers, and all the other Kubernetes entities they belong to). The idea behind it is that you should use a distributed monitoring and troubleshooting tool like Sysdig Cloud to keep an eye on your overall cluster and, when needed, zoom into a specific node using a lower level tool such as sysdig/csysdig. |
We use cert-based auth to talk with our kubernetes v1.1.1 API server. I don't see a way to talk to it with
csysdig
. Sysdig Cloud does work.The text was updated successfully, but these errors were encountered: