Chart name and version, where you feel a lack of requested feature
chart: victoria-metrics-k8s-stack, victoria-logs-single (all other as well, but I am not planning to use them)
Is your feature request related to a problem? Please describe.
I follow best practices and require explicitly allowing network connections for each application (I have a global deny all network policy by default). Other widely used charts provide opportunity to enable network policies by default (see grafana helm chart code, cert manager network policy documentation, etc).
Describe the solution you'd like
A helm chart value flag, like networkPolicy.enabled. This shall create Kubernetes native Network Policies allowing all the necessary connections and be extendable (in case some use cases are not covered). Next step might be to enable support for some other popular CNIs Network Policy CRs (e.g. Calico Network Policies)
Describe alternatives you've considered
So far, I had to create my own chart and put (by now deprecated) vm-distributed chart as subchart to implement network Policies (see https://github.com/ITISFoundation/osparc-ops-environments/tree/main/charts/victoria-metrics-distributed/templates/networkpolicies). I think I might have tried to put all of them in extraObjects but it quickly get over-polluted (if you have 6-8 policies).
Additional context
I like how grafana did it. You can easily enable network policy and also extend it (yeah, if default values are not covering all use cases of your configuration). See example https://github.com/ITISFoundation/osparc-ops-environments/blob/main/charts/grafana/values.yaml.gotmpl#L2-L13
Chart name and version, where you feel a lack of requested feature
chart:
victoria-metrics-k8s-stack,victoria-logs-single(all other as well, but I am not planning to use them)Is your feature request related to a problem? Please describe.
I follow best practices and require explicitly allowing network connections for each application (I have a global deny all network policy by default). Other widely used charts provide opportunity to enable network policies by default (see grafana helm chart code, cert manager network policy documentation, etc).
Describe the solution you'd like
A helm chart value flag, like
networkPolicy.enabled. This shall create Kubernetes native Network Policies allowing all the necessary connections and be extendable (in case some use cases are not covered). Next step might be to enable support for some other popular CNIs Network Policy CRs (e.g. Calico Network Policies)Describe alternatives you've considered
So far, I had to create my own chart and put (by now deprecated)
vm-distributedchart as subchart to implement network Policies (see https://github.com/ITISFoundation/osparc-ops-environments/tree/main/charts/victoria-metrics-distributed/templates/networkpolicies). I think I might have tried to put all of them inextraObjectsbut it quickly get over-polluted (if you have 6-8 policies).Additional context
I like how grafana did it. You can easily enable network policy and also extend it (yeah, if default values are not covering all use cases of your configuration). See example https://github.com/ITISFoundation/osparc-ops-environments/blob/main/charts/grafana/values.yaml.gotmpl#L2-L13