OAuth2 Proxy Advanced Helm Chart
OAuth2 Proxy is a reverse proxy and static file server that provides authentication using Providers (Google, GitHub, and others) to validate accounts by email, domain or group. The OAuth2 Proxy Advanced Helm chart automates deployment and configuration of OAuth2 Proxy in Kubernetes clusters using Minimus images with hardened security and production-grade configuration.
Prerequisites
- A subscription to the Minimus images included in the chart
- A running Kubernetes cluster (v1.21 or higher is recommended)
kubectl installed and configured- Helm v3.8 or higher for OCI support (Installation instructions)
- Cluster Admin privileges
- OAuth2 credentials from your identity provider (Google, GitHub, Azure AD, etc.) — client ID, client secret, and a 16/24/32-byte cookie secret
Note: OAuth2 Proxy will not start with the chart's defaults — a provider and credentials must be supplied through your own values.yaml (see Step 3). Refer to the oauth2-proxy configuration docs for the full list of supported providers and options.
Try It Out
In this example we will deploy OAuth2 Proxy on a Kubernetes cluster using the Minimus OAuth2 Proxy Advanced Helm chart. OAuth2 Proxy will be configured with hardened security settings and production-grade defaults.
Step 1: Start Cluster
If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions
Step 2: Create Namespace
Create a namespace:
kubectl create ns oauth2-proxy-advanced
Step 3: Deploy the Helm Chart
Deploy the Minimus Helm chart:
helm install my-oauth2-proxy-advanced oci://helm.mini.dev/oauth2-proxy-advanced \
--version 8.0.2 \
-n oauth2-proxy-advanced \
--wait
If you want to override the chart's defaults, go to the Values tab, save a copy locally with your changes. Deploy the chart with your overrides using -f values.yaml:
helm install my-oauth2-proxy-advanced oci://helm.mini.dev/oauth2-proxy-advanced \
--version 8.0.2 \
-f values.yaml \
-n oauth2-proxy-advanced \
--wait
Step 4: Verify OAuth2 Proxy Advanced is Running
Check the pod status:
kubectl get pods -n oauth2-proxy-advanced -l app.kubernetes.io/name=oauth2-proxy
You should see output similar to:
NAME READY STATUS RESTARTS AGE
my-oauth2-proxy-advanced-xxxxxxxxx-xxxxx 1/1 Running 0 1m
Step 5: Test HTTP Endpoint
Port-forward to the OAuth2 Proxy service:
kubectl port-forward svc/my-oauth2-proxy-advanced 4180:4180 -n oauth2-proxy-advanced
In another terminal, hit the /ping health endpoint:
curl -sf http://localhost:4180/ping
You should receive an HTTP 200 response.
Step 6: Clean Up
Uninstall the chart and delete the namespace to remove all resources:
helm uninstall my-oauth2-proxy-advanced -n oauth2-proxy-advanced
kubectl delete namespace oauth2-proxy-advanced
Terms & Info
Trademark
This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.
Disclaimer
Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.
