-
Notifications
You must be signed in to change notification settings - Fork 14
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
The operator fails to scan GKE autopilot clusters #850
Comments
Seems that the problem is that we have this volume
Which gets mounted here:
Which causes the following error
I see that we are currently relying on this volume for scanning
I don't have a solution currenlty, just wanted to share my insights from taking a first look at this problem. I assume we should at least be able to build better handling around this case as this currently prevents the cronjob from being created at all. |
Seeing that if node scanning fails we just stop and don't even attempt to scan kubernetes ressources - I wonder if for autopilot clusters we could be fine with being unable to scan the nodes (currently I don't see a way to make that work) but still scan the resources in the cluster
|
Thanks @mariuskimmina, for digging deeper into this. It's good to know what to look for. Perhaps other ways to scan a now work in GKE autopilot. |
Describe the bug
When the operator is deployed in a GKE autopilot cluster, it does not report any assets.
https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview
This needs to be fixed because the new default for GKE clusters is autopilot: https://cloud.google.com/blog/products/containers-kubernetes/gke-autopilot-is-now-default-mode-of-cluster-operation
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The operator should scan the same workloads as in other clusters.
The text was updated successfully, but these errors were encountered: