trivy-operator
trivy-operator copied to clipboard
Have only one source of configuration
Currently, there is two separate ways to configure trivy-operator settings. There are settings configured as environment variables to the deployment, and some other options configured in a configmap. This leads to complexity in code, for example, all controllers receive etc.Config
and also trivyoperator.ConfigData
which represent the different way of configuring trivy-operator. Also, from a UX point, it is preferable to change configurations on a configmap then restart the pod, simpler than changing an env var on a deployment.
@chen-keinan Do you mind if I take this issue?
@josedonizetti thanks for picking this up! This would be a very nice improvement!
@josedonizetti was the mentioned pull request pending more development or pending review when it was closed for being stale?