Kube Enforcer's starboard operator to trivy operator migration about aqua-helm HOT 1 CLOSED

Hi @tnycum
Sorry for the delay in the response. Here are my responses to your queries

1. Ideally latest Trivy-operator should work fine, but as trivy-operator is adding new feature regularly, so there might be few settings we will enable/disable to make it work properly. So we internally perform QA before updating to latest version. Currently it is updated to 0.16.1 version.
2. We captured documentation around trivy-operator, as we were not done with Sizing guide, we brought back starboard as default option. From migration point of view, removing KubeEnforcer+starboard and installing with KubeEnforcer+trivyOperator should take care of migration. We shouldnt have change in our findings from cluster except underline change in the engine(ie. instead of starboard, we will see trivy-operator)
3. Yes there is version compatibility required for Trivy-operator to work. Update 24 or higher version of KubeEnforcer is required to work with trivy-operator. Lower will not work properly. New KubeEnforcer version(u24 and later) is capable to work with Trivy-operator and starboard, So either of them can be deployed with KubeEnforcer.

Thank you for raising these queries, we will capture them once we make Trivy-operator as default option.

Regards,
Devendra

from aqua-helm.