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
No severeties #27
Comments
Looks like there were failures during the scan, can you please share logs from all Kubei components and from the klar-scanner pods? You can use the following:
|
1st:
|
2nd with grep ( too large ouput)
|
PostgreSQL:
|
xargs:
|
It seems that all the communication in the cluster is blocked |
can u tell me how can i check it or correct? |
|
|
Please share more info on your environment, how it was installed, platform, etc.. Did you tried to deploy a sleep app and run a simple curl command?
|
Centos7 - baremetal
|
I'm not sure but it look you have a problem with the cluster configuration. DNS resolving is not working properly. |
DNS seems fine:
|
I'm not very familiar with DNS configuration. Is google being resolved when you run Does the |
|
A default K8s cluster should have the ability of pod-to-pod communication and also pod to external (out of cluster) destinations without any special configuration. Looks like some modifications where made that prevent it (e.g. vendor fw rules, iptables rules, etc). Please try to install Kubei on a cluster that allows internal and external (outbound) communication. |
Hi!
After running the scanner, I got some report.
However, it has no severity levels.
Did I something wrong?
I also have a lot of dead pods, created by kubernetes jobs
The text was updated successfully, but these errors were encountered: