New feature: network policies (1.9.0)

[anthosz]

Descriptive description goes here.

Tasks:

• I've made changes
• I've bumped chart's version in Chart.yaml
• I've added changes to charts CHANGELOG.md
• I've run helm-docs

Fixes: #50

[MaikuMori]

It's currently failing test:

Error: UPGRADE FAILED: template: gotenberg/templates/networkpolicy.yaml:1:14: executing "gotenberg/templates/networkpolicy.yaml" at <.Values.networkPolicy.enabled>: nil pointer evaluating interface {}.enabled

This happens because of how helm upgrades charts. To fix it you need to check if networkPolicy exists before checking if enabled in truthy.

This issue only happens on upgrades, not fresh installs.

[anthosz]

It's currently failing test:

Error: UPGRADE FAILED: template: gotenberg/templates/networkpolicy.yaml:1:14: executing "gotenberg/templates/networkpolicy.yaml" at <.Values.networkPolicy.enabled>: nil pointer evaluating interface {}.enabled

This happens because of how helm upgrades charts. To fix it you need to check if networkPolicy exists before checking if enabled in truthy.

This issue only happens on upgrades, not fresh installs.

Patch pushed + aligned with master

[MaikuMori]

I'm going to add a couple changes too so it's bundled in the same release.

[MaikuMori]

This seems a bit weird way to structure it, but I think it's ok for now. We can always accept a PR to change it.

[anthosz]

Indeed, I copy paste from my PR for varnish, varnish/helm-varnish-cache#24

It's not really clean but it allow to unblock when we use strict mode on cni :)

TODO: add a default schema that took into account the port & probably a matchexpressions based on ns or pod selector

Thank you!