Skip to content

Conversation

mjshastha
Copy link
Contributor

@mjshastha mjshastha commented Nov 7, 2024

With this implementation, we are migrating from starboard operator to trivy operator:

  1. We have updated kube_enforcer,kube_enforcer_advanced manifest files with Trivy Operator Resources
  2. Updated relevant gen_ke_certs.sh and readme files
  3. Upgraded trivy-operator version to latest (0.22.0)as the existing version has critical vulnerabilities.

@mjshastha mjshastha force-pushed the migratingToTrivyOperator branch from 8a53f95 to 4ed0ee6 Compare April 2, 2025 12:53
@mjshastha mjshastha force-pushed the migratingToTrivyOperator branch 4 times, most recently from 494dd62 to 08b1095 Compare April 18, 2025 08:53
- name: OPERATOR_EXCLUDE_NAMESPACES
value: "kube-system"
- name: OPERATOR_TARGET_WORKLOADS
value: "pod,replicaset,replicationcontroller,statefulset,daemonset,cronjob,job"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we cross check if we dont need deployment here

@mjshastha mjshastha force-pushed the migratingToTrivyOperator branch from 08b1095 to a3481b9 Compare April 24, 2025 14:49
… trivy operator:

1. We have updated kube_enforcer,kube_enforcer_advanced manifest files with Trivy Operator Resources
2. Updated relevant gen_ke_certs.sh and readme files
3. Upgraded trivy-operator version to  latest (0.25.0)as the existing version has critical vulnerabilities.
@mjshastha mjshastha force-pushed the migratingToTrivyOperator branch from c5648a1 to 08434bb Compare April 30, 2025 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants