Zora is an open source solution that helps you achieve compliance with Kubernetes best practices recommended by industry-leading frameworks. By scanning your cluster with multiple plugins, Zora identifies potential issues, misconfigurations, and vulnerabilities.
There's a bug in the \<ClusterScan> controller where the \<IssueCount> field from
all instances of the \<PluginScanStatus> struct within the \<Plugins> map were
given the same pointer, thus carrying the same value, what appeared as an
incorrect sum when checking each plugin's issue count.
This is fixed in this commit.
How has this been tested?
With local deployments on a virtual cluster pointing to the Hml cluster where
the bug was discovered and go-test as well.
Checklist
[x] I have labeled this PR with the relevant Type labels
Description
There's a bug in the \<ClusterScan> controller where the \<IssueCount> field from all instances of the \<PluginScanStatus> struct within the \<Plugins> map were given the same pointer, thus carrying the same value, what appeared as an incorrect sum when checking each plugin's issue count.
This is fixed in this commit.
How has this been tested?
With local deployments on a virtual cluster pointing to the Hml cluster where the bug was discovered and go-test as well.
Checklist