# kube-rbac-proxy

kube-rbac-proxy is a lightweight HTTP proxy for a single upstream that enforces Kubernetes role-based access control (RBAC) authorization by validating each request's token or client TLS certificate against the cluster. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/5865/kube-rbac-proxy

## Description

Kube RBAC Proxy is a lightweight HTTP proxy for a single upstream that enforces Kubernetes role-based access control (RBAC) authorization by validating each request's token or client TLS certificate against the cluster API. It lets you protect internal services, such as monitoring dashboards, so that only users with the required permissions can reach them.

## Platform availability

Available on 0 of 10 platforms.

## Health score

70/100 (Good), based on 4 of 5 factors.
- Maintained: 91 (last commit 24 days ago)
- Popular: 57 (690 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)
- Security check: 88 (no serious findings, CI, tests, OpenSSF Scorecard 6.9/10)

## Links

- GitHub: https://github.com/brancz/kube-rbac-proxy
- Docker Hub: https://hub.docker.com/r/bitnami/kube-rbac-proxy

## Common questions

### Can kube-rbac-proxy proxy to more than one upstream?

No, it is described as a small HTTP proxy for a single upstream.

### How is kube-rbac-proxy configured?

It is configured primarily through command line flags and an optional YAML configuration file.

### How does kube-rbac-proxy authorize incoming requests?

It performs RBAC authorization against the Kubernetes API using SubjectAccessReview. It can restrict requests to those presenting a valid RBAC authorized token or client TLS certificate.

### Are flags and behavior stable across releases?

The project is still alpha, so flags, configuration, behavior, and design may change significantly. It is also deprecating some features to align more tightly with Kubernetes.

### What can cause kube-rbac-proxy to crashloop in an OpenShift monitoring stack?

A reported case attributed openshift-monitoring being down to a prometheus-operator issue that left the kube-rbac-proxy container failing and stuck in a CrashLoopBackOff.

---
Source: Our Local Host (https://ourlocalhost.com/app/5865/kube-rbac-proxy), the self-hosted and open-source app directory.
