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
I discovered your Kube Downscaler chart recently and decided to use it.
I'd like to propose something like shown below for configuring downscaler, instead of relying in raw definition of keys in env block:
# values.yamlconfig:
# default empty values to avoid impact in a installations and be backward compatible with previous usage of env blockdefaultUptime: ""defaultDowntime: ""dowscalePeriod: ""namespace:
activeIn: ""inactiveIn: ""
the fields namespace.activeIn and namespace.inactiveIn are inspired in this helm-chart: https://github.com/hahow/kube-downscaler, I found it easy to understand. Those values would be read from a ConfigMap and used in the deployment.
If you approve this idea, I can make a PR.
The text was updated successfully, but these errors were encountered:
Hi,
I discovered your Kube Downscaler chart recently and decided to use it.
I'd like to propose something like shown below for configuring downscaler, instead of relying in raw definition of keys in
env
block:the fields
namespace.activeIn
andnamespace.inactiveIn
are inspired in this helm-chart: https://github.com/hahow/kube-downscaler, I found it easy to understand. Those values would be read from a ConfigMap and used in the deployment.If you approve this idea, I can make a PR.
The text was updated successfully, but these errors were encountered: