[kube-state-metrics] Add selfMonitor.telemetryNodePort field to values

[AlexHill]

What this PR does / why we need it:

Adds a selfMonitor.telemetryNodePort field to values.yaml so that a NodePort for the telemetry endpoint can be specified when service.type is set to NodePort.

Special notes for your reviewer:

Tagging @tariq1890 @mrueg @dotdc as per the PR template comment.

There is a slight incongruence here in that if selfMonitor.telemetryNodePort is specified but service.type is not set to NodePort, the deployment will fail. Options to fix, if desired:

• put the telemetry endpoint fields under service
• create separate Services for telemetry and core metrics
• set the Service type to NodePort if either service.nodePort or selfMonitor.telemetryNodePort are specified

(In the existing chart, the deployment will also fail if services.nodePort is non-zero while services.type is not NodePort - but that's a bit less surprising since the dependent fields are all under the services top-level key.)

Checklist

• DCO signed
• Chart Version bumped
• Title of the PR starts with chart name (e.g. [prometheus-couchdb-exporter])

[dotdc]

Hi @AlexHill,

I think it's ok to merge as is if you add the limitation in the comment block (see my review)

[AlexHill]

Hi @dotdc, thanks for the extremely quick response!

Not sure what's going on but I can't see your review. In any case though I've added a comment now.

[dotdc]

LGTM

[dotdc]

My bad, the review was still pending. Anyway the comment is basically what I suggested.
Thank you for your contribution!