trivy-operator integration with kube-enforcer #568
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With this change, we are replacing starboard operator with trivy operator
We have updated kube_enforcer,kube_enforcer_advanced manifest files with Trivy Operator Resources
Moved starboard manifest files to kube_enforcer_starbaord and kube_enforcer_advanced_starboard
Updated relevant gen_ke_certs.sh and readme files
Reference PR: trivy-operator integration with kube-enforcer #566
Upgraded trivy-operator version to latest (0.20.1)as the existing version has critical vulnerabilities
Upgraded kube-bench version with latest (v0.7.3)
Reference PR: chore: kube-bench & trivy-operator version upgrade #567
Added keys for Admission Control when the GW is disconnected, Enable workload discovery, Register discovered pod images, and Add discovered registries.
Removed the AQUA_WATCH_CONFIG_AUDIT_REPORT key as it is no longer supported.
Reference PR: Update deployments yamls with new fields in KE configmap. #565