You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the scs-health-monitor is executed in a Docker container, it would be useful if all configuration files could be stored in a dedicated directory (clouds.yaml, env.yaml and ~/.kube/config). This would reduce the number of mounts and also make it much easier to run scs-health-monitor in a non-root container.
My suggestion would be that this is controlled via an environment variable SCS_HEALTH_MONITOR_CONFIG_DIR (i.e. <BASEDIR>/config).
The Openstack searchpath should be controllable via OpenStackConfig(config_files=[config_dir]), in the kubernetes client with the KUBE_CONFIG variable, and env.yaml seems to be a custom config for the tool.
The text was updated successfully, but these errors were encountered:
If the scs-health-monitor is executed in a Docker container, it would be useful if all configuration files could be stored in a dedicated directory (clouds.yaml, env.yaml and ~/.kube/config). This would reduce the number of mounts and also make it much easier to run scs-health-monitor in a non-root container.
My suggestion would be that this is controlled via an environment variable
SCS_HEALTH_MONITOR_CONFIG_DIR
(i.e.<BASEDIR>/config
).The Openstack searchpath should be controllable via
OpenStackConfig(config_files=[config_dir])
, in the kubernetes client with theKUBE_CONFIG
variable, and env.yaml seems to be a custom config for the tool.The text was updated successfully, but these errors were encountered: