Deprecate or Remove kube rbac proxy server in CAPC

[rajeshvenkata]

This is about CAPC upgrade from v0.5.0 to v0.6.0. When we were testing the CAPC upgrade, cluster creation failed because CAPC controller pod kept crashing due to the 8443 port conflicts from kube-rbac-proxy and CAPI diagnostic feature (enabled in v0.6.0)

Looks like int the past, rbac proxy was added as a workaround to serve metrics. With diagnostic feature enabled, I believe this rbac proxy is not needed because CAPI diagnostic feature now servers the same purpose - serving metrics endpoint via https (8443)and protected via authentication and authorization.

Given that is it not needed now and also the port conflicts issue, we are proposing to remove the kube-rbac-proxy in the CAPC. Looking forward to your thoughts on this. Thanks!

[yadvr]

cc @vishesh92 @weizhouapache @harikrishna-patnala - please review & advise.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[vishesh92]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten