Capsule Proxy

Capsule Proxy is a Kubernetes add-on for teams using the Capsule multi-tenancy operator that proxies tenant cluster-scoped resource lookups and reduces…

  • Infrastructure
  • Network Services
Capsule Proxy is a Kubernetes add-on for teams using the Capsule multi-tenancy operator that proxies tenant cluster-scoped resource lookups and reduces control-plane load.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

69/100 Good

Maintained
100last commit 16 days ago
Popular
3665 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
90no serious findings, 1 minor, CI, tests, OpenSSF Scorecard 8.3/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
65
Open issues
14
Last commit
2026-11-05
Latest release
v0.15.3
License
Apache-2.0
Activity
steady

Checked 14 days ago - source: GitHub (projectcapsule/capsule-proxy)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Start the playground Run make up from the playground directory to create a small local cluster and install Capsule, Capsule Proxy, Dex (a login system), Headlamp (a web dashboard), and ingress-nginx (a web traffic router) through Flux (an automated installer for Kubernetes apps). This is the main step that puts the pieces you need on the cluster, so skipping it means Capsule Proxy is not running. source
  • Set up the sample permits Use kubectl (the Kubernetes command-line tool) to apply the two example permit templates, then submit the sample permit requests as alice after solar-system appears in each template's status.namespaces (the list of created namespaces). This first-run step gives the example user access to the sample namespace and avoids request failures. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need to grant tenants LIST permissions on cluster-scoped resources when using Capsule multi-tenancy?

No, capsule-proxy is described as addressing that RBAC limitation. The docs note granting all users LIST permissions for relevant cluster-scoped resources as a possible workaround.

Which cluster-scoped resources are specifically named as covered?

Namespaces, Ingress resources, Storage Classes, and Nodes are named, and the project description implies others are covered as well.

Is capsule-proxy a general reverse proxy for arbitrary self-hosted applications?

No, it is described as an add-on for Capsule, the operator providing multi-tenancy in Kubernetes.

Where should self-hosters file problems or feature requests?

The GitHub Issues page is listed as the place to contribute to project development.

Answers sourced from github.com, github.com, projectcapsule.dev

Community

Collected 48 days ago - public community threads