Add namespace to chart, support for custom namespace

[kruchkov-alexandr]

Summary of Changes

• Namespace Support: Added namespace field to cert-manager.yaml, service.yaml, and values.yaml with a default value of monitoring.
• Tag Update: Made the tag field in values.yaml customizable, defaulting to .Chart.AppVersion.

These changes enhance flexibility for namespace configuration and image tag management.

Local tests for another namespace:

helm upgrade \
  --install cert-exporter helm/cert-exporter/ \
  --set certManager.namespace=service \
  --set dashboards.namespace=service \
  --values helm/cert-exporter/values.yaml

[kruchkov-alexandr]

@joe-elliott hey
please take a look at this pull request. Thanks!

[joe-elliott]

howdy! thanks for the PR. i've been meaning to get to this.

i think my only question is: will this impact folks who have installed cert-exporter in namespaces besides "monitoring" when they go to upgrade?

[kruchkov-alexandr]

It shouldn't be an issue at all, as far as I understand.
That's exactly why I created the pull request so you could review it =)

[joe-elliott]

I just don't really know much about helm and this chart is basically community maintained. I do value not changing things unnecessarily if its basically working for folks. If this is a valuable improvement I'll merge it, but I need to know it won't negatively impact people currently using the chart.

[CarstenSon]

hey @kruchkov-alexandr 😄

Would you mind making the namespace optional (e.g. using if/with) in the helm-chart? Since it's not a required field in the underlying k8s spec that would make it a non-breaking change for folks who don't have the namespace set currently. I often work with Bearer tokens that are only entitled for certain namespaces and like the minimal approach of the current helmchart.

If this was optional my setup wouldn't be concerned/affected at all - with the current implementation it would be a breaking change as I'd need to set the namespace for each deployment of cert-exporter :/