Chainguard Container for kube-rbac-proxy

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/kube-rbac-proxy:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The Chainguard kube-rbac-proxy container image is comparable to the upstream kube-rbac-proxy project maintained by Brancz. As with other Chainguard Containers, the kube-rbac-proxy image was designed with minimalism in mind, and therefore doesn't contain things like a shell or package manager.

Getting Started

The kube-rbac-proxy is a small HTTP proxy for a single upstream that can perform RBAC authorization against the Kubernetes API. It's commonly used to protect metrics endpoints.

Basic Usage

You can test the image by running it directly:

docker run --rm cgr.dev/ORGANIZATION/kube-rbac-proxy:latest

This will display the help text for kube-rbac-proxy.

Kubernetes Deployment

Here's a complete example of deploying kube-rbac-proxy in a Kubernetes cluster to protect a metrics endpoint:

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: kube-rbac-proxy
rules:
  - apiGroups: ["authentication.k8s.io"]
    resources:
      - tokenreviews
    verbs: ["create"]
  - apiGroups: ["authorization.k8s.io"]
    resources:
      - subjectaccessreviews
    verbs: ["create"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: kube-rbac-proxy
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: kube-rbac-proxy
subjects:
  - kind: ServiceAccount
    name: kube-rbac-proxy
    namespace: default
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: kube-rbac-proxy
  namespace: default
spec:
  replicas: 1
  selector:
    matchLabels:
      app: kube-rbac-proxy
  template:
    metadata:
      labels:
        app: kube-rbac-proxy
    spec:
      serviceAccountName: kube-rbac-proxy
      containers:
        - name: kube-rbac-proxy
          image: cgr.dev/ORGANIZATION/kube-rbac-proxy:latest
          args:
            - "--secure-listen-address=0.0.0.0:8443"
            - "--upstream=http://127.0.0.1:8081/"
            - "--v=10"
          ports:
            - containerPort: 8443
              name: https
        - name: prometheus-example-app
          image: quay.io/brancz/prometheus-example-app:v0.5.0
          args:
            - "--bind=127.0.0.1:8081"
---
apiVersion: v1
kind: Service
metadata:
  labels:
    app: kube-rbac-proxy
  name: kube-rbac-proxy
  namespace: default
spec:
  ports:
    - name: https
      port: 8443
      targetPort: https
  selector:
    app: kube-rbac-proxy
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: kube-rbac-proxy
  namespace: default

This example sets up:

• A ClusterRole with permissions for token and subject access reviews
• A deployment with kube-rbac-proxy protecting a sample Prometheus app
• The proxy listens on port 8443 and forwards to the upstream service on port 8081

Documentation and Resources

• kube-rbac-proxy GitHub Repository
• Kubernetes RBAC Documentation
• Prometheus Operator Documentation

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.