Commits on Jun 14, 2024

1. Allow loading secrets from a separate config file …

   Currently all config is in a kubernetes secret because some of the
   config keys the helm chart renders might be secrets.
   
   This is a problem, as a lot of people don't want to, or don't have the
   option to manage secrets with helm (eg. secret management is fully
   decoupled from helm deployments).
   
   To fix this, utilize go viper's solution that allows deep-merging
   multiple config file contents. This allows for splitting out the
   potentially sensitive keys into a separate config file, and then having
   viper merge them back together.
   
   The helm chart was modified so it retains backward compatibility with
   the `existingTargetConfig` config option. If that key exists then it
   is assumed that it is a kubernetes secret (as before), and the
   separation of config values and secrets is not performed by the chart.
   
   This PR should be able fixes kyverno#454
   
   Signed-off-by: Zoltán Reegn <zoltan.reegn@gmail.com>

   

   reegnz committed Jun 14, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for f9af63b
   • Browse repository at this point

   Copy the full SHA

   f9af63b View commit details

   Browse the repository at this point in the history