Add initial implementation of gitea-mcp-forward-auth microservice
Build and Test / verify (push) Failing after 22s

- Create build and release workflows for CI/CD
- Implement Dockerfile for multi-stage builds
- Add core authentication logic with token validation
- Include HTTP handler for authorization checks
- Set up Kubernetes deployment and service manifests
- Update README with usage instructions and configuration details
This commit is contained in:
2026-07-11 21:58:58 +02:00
parent 75acb3c376
commit ea4aac6641
11 changed files with 603 additions and 1 deletions
+50
View File
@@ -0,0 +1,50 @@
apiVersion: apps/v1
kind: Deployment
metadata:
name: gitea-mcp-auth-proxy
labels:
app: gitea-mcp-auth-proxy
spec:
replicas: 1
selector:
matchLabels:
app: gitea-mcp-auth-proxy
template:
metadata:
labels:
app: gitea-mcp-auth-proxy
spec:
containers:
- name: auth-proxy
image: gitea.nehmer.net/torben/gitea-mcp-auth-proxy:latest
imagePullPolicy: IfNotPresent
ports:
- containerPort: 8080
name: http
env:
- name: AUTH_PROXY_LISTEN_ADDR
value: ":8080"
- name: AUTH_PROXY_TOKENS_DIR
value: /var/run/secrets/auth-proxy
- name: AUTH_PROXY_LOG_LEVEL
value: info
volumeMounts:
- name: auth-tokens
mountPath: /var/run/secrets/auth-proxy
readOnly: true
readinessProbe:
httpGet:
path: /healthz
port: http
initialDelaySeconds: 2
periodSeconds: 10
livenessProbe:
httpGet:
path: /healthz
port: http
initialDelaySeconds: 5
periodSeconds: 15
volumes:
- name: auth-tokens
secret:
secretName: gitea-mcp-auth-proxy-tokens
+15
View File
@@ -0,0 +1,15 @@
apiVersion: v1
kind: Service
metadata:
name: gitea-mcp-auth-proxy
labels:
app: gitea-mcp-auth-proxy
spec:
selector:
app: gitea-mcp-auth-proxy
ports:
- name: http
port: 80
targetPort: http
protocol: TCP
type: ClusterIP