Skip to content

remove kube-rbac-proxy reference - #261

Merged
sasikanthmasini merged 3 commits into
mainfrom
remove-kube-rbac-proxy
Sep 10, 2026
Merged

sasikanthmasini merged 3 commits into
mainfrom
remove-kube-rbac-proxy

Conversation

@shivaprasadmb

@shivaprasadmb shivaprasadmb commented Sep 4, 2026 •

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:
This PR is to remove kube-rbac-proxy sidecar container from ndb-operator and utilieze controller runtime native authorization to secure metrics server.

Kube-rbac-proxy mainly helps to secure http communications to access controller metrics using token. Since the newer versions of operator-sdk and kube-builder have native support for the same kuberbac-proxy can be removed.

Advantages:

  • reduces one container from ndb-operator.
  • helps in reducing dependency on 3rd party tools.
  • simplifies vulnerability management.

How Has This Been Tested?:

The testing is done based on kube-rbac-proxy capabilities. Comparison is done to check functionalities before and after removing kube-rbac-proxy.

Before removing kube-rbac-proxy

Screenshot 2026-09-07 at 10 05 53 AM Screenshot 2026-09-07 at 10 06 01 AM Screenshot 2026-09-07 at 10 07 11 AM

After removing kube-rbac-proxy

Screenshot 2026-09-07 at 11 08 40 AM Screenshot 2026-09-07 at 11 08 42 AM Screenshot 2026-09-07 at 11 17 31 AM Screenshot 2026-09-07 at 11 17 52 AM

Special notes for your reviewer:

  • removing kube-rbac-proxy helps in reducing dependency and maintain CVEs easily.

Release note:

use latest operator sdk version.
remove kube-rbac-proxy support.

@sasikanthmasini sasikanthmasini left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@sasikanthmasini
sasikanthmasini merged commit dd7df9c into main Sep 10, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants