Kube-bench Incompatible with OKE: configuration is missing in "cfg/" for oke #1938
Replies: 3 comments
-
|
Hi, Thanks again for highlighting this gap! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the quick response and for confirming that OKE-specific configuration support will be there, really appreciate the clarity! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @shreyansh2953, We’ll share updates as soon as we have clearer progress. In the meantime, if you happen to explore or draft any OKE-specific mappings on your side, please do share — it could help us accelerate the work. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Kube-bench Team, @LaibaBareera @afdesk
We’re currently working on integrating Kube-bench into our Oracle Kubernetes Engine (OKE) environment to generate vulnerability reports for our worker nodes.
Environment: Oracle Kubernetes Engine (OKE)
Kube-bench Version: 0.1.17
App Version: 0.8.0
Command Used: ["kube-bench", "run", "--targets", "node", "--benchmark", "cis-1.24"]
While executing the above command, we encountered failures in certain checks.

Here’s a snapshot of the issue:
Upon investigation, we referred to the CIS Benchmark for OKE v1.7.0 provided by Oracle. The benchmark outlines several environment-specific configurations. A few examples include:
But in comman config.yaml under cfg folder provided by kube-bench we were unable to find the location( /etc/kubernetes/kubelet-config.json) :-

and we saw in cfg folder that aquasecurity team has developed the cfg for different cloud providers like aks-1.7 , eks-1.9 etc. compatible to that env
so can we expect the same development for OKE env so that in command we can use something like oke-1.7 for cis benchmarking
Beta Was this translation helpful? Give feedback.
All reactions