Fix port allocation for node-exporter

[steve-wolter-ai]

Description

The daemonset for the node exporter is statically invalid. It assigns port 9100 both to the node-exporter container and to the kube-rbac-proxy container.

This results in the following behavior at runtime:

1. kube-rbac-proxy and node-exporter race for port 9100.
2. If kube-rbac-proxy wins, the system functions normally. However, kube-rbac-proxy is disfunctional and does NOT actually check authorization.
3. If kube-rbac-proxy wins, it fails to locate its upstream and crashes. The race restarts.

This change is somewhat risky as we've been (so far) rolling out node-exporter with no kube-rbac-proxy, and would now unmasks any bugs in the kube-rbac-proxy integration.

Type of change

What type of changes does your code introduce to the kube-prometheus? Put an x in the box that apply.

• CHANGE (fix or feature that would cause existing functionality to not work as expected)
• FEATURE (non-breaking change which adds functionality)
• BUGFIX (non-breaking change which fixes an issue)
• ENHANCEMENT (non-breaking change which improves existing functionality)
• NONE (if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)

Changelog entry

Activate kube-rbac-proxy for node-exporter.