github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-21 09:21:15 -05:00
Code Issues 856 Packages Projects Releases 74 Wiki Activity

[PR #2615] [CLOSED] Add kustomize manifests for Kubernetes deployment #3060

New Issue
Closed
opened 2026-04-16 09:46:34 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-16 09:46:34 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/fosrl/pangolin/pull/2615
Author: @Br1an67
Created: 3/7/2026
Status: ❌ Closed

Base: main ← Head: fix/issue-921-fix-921

📝 Commits (1)

  • a0c2508 feat(kubernetes): add kustomize manifests for deployment

📊 Changes

5 files changed (+526 additions, -0 deletions)

View changed files

➕ kustomize/README.md (+294 -0)
➕ kustomize/base/gerbil-deployment.yaml (+118 -0)
➕ kustomize/base/kustomization.yaml (+11 -0)
➕ kustomize/base/namespace.yaml (+7 -0)
➕ kustomize/base/pangolin-deployment.yaml (+96 -0)

📄 Description

Fixes #921

Community Contribution License Agreement

By creating this pull request, I grant the project maintainers an unlimited,
perpetual license to use, modify, and redistribute these contributions under any terms they
choose, including both the AGPLv3 and the Fossorial Commercial license terms. I
represent that I have the right to grant this license for all contributed content.

Description

This PR adds Kubernetes deployment manifests using kustomize, enabling users to deploy Pangolin on Kubernetes clusters. This addresses the community request for Kubernetes support as discussed in #921.

The implementation includes:

  • Pangolin server deployment with health checks and resource limits
  • Gerbil + Traefik deployment using a sidecar pattern (matching the docker-compose architecture where traefik shares gerbil's network namespace)
  • Persistent storage for configuration and data
  • LoadBalancer service for external access (WireGuard ports + HTTP/HTTPS)
  • Comprehensive documentation with deployment guides and troubleshooting tips

Architecture

The deployment follows the docker-compose structure:

  1. Pangolin - Main application server (port 3001)
  2. Gerbil + Traefik - Combined pod with sidecar pattern:
    • Gerbil: WireGuard VPN tunnel (ports 51820, 21820 UDP)
    • Traefik: Reverse proxy (ports 80, 443 TCP)
    • Shares network namespace like in docker-compose

Key Features

  • Uses official images: fosrl/pangolin:latest, fosrl/gerbil:latest, traefik:v3.6
  • Proper capability management (NET_ADMIN, SYS_MODULE for Gerbil)
  • Health checks and readiness probes
  • Configurable resource limits
  • Single PVC for all config data (can be separated for production)
  • Kustomize-ready structure with base layer

How to test?

Prerequisites

  • Kubernetes cluster (1.24+)
  • kubectl configured
  • Persistent volume provisioner
  • LoadBalancer support (or use NodePort/Ingress)

Quick Test

  1. Create namespace and deploy:

    kubectl apply -k kustomize/base

  2. Verify deployment:

    kubectl get all -n pangolin
kubectl logs -n pangolin -l app.kubernetes.io/name=pangolin

  3. Check pod status:

    kubectl get pods -n pangolin

    Expected output:

    NAME                       READY   STATUS    RESTARTS   AGE
pangolin-xxx-xxx          1/1     Running   0          1m
gerbil-xxx-xxx            2/2     Running   0          1m

  4. Verify services:

    kubectl get svc -n pangolin

    Expected services:

    • pangolin (ClusterIP on port 3001)
    • gerbil (LoadBalancer with ports 80, 443, 51820, 21820)

Configuration Testing

Before production use, you'll need to:

  1. Create a config.yml based on config/config.example.yml
  2. Set up Traefik configuration in config/traefik/
  3. Configure database (SQLite or external PostgreSQL)

See kustomize/README.md for detailed configuration instructions.

Validation

All YAML files have been validated for syntax:

# Validate YAML syntax
python3 -c "import yaml; list(yaml.safe_load_all(open('kustomize/base/pangolin-deployment.yaml')))"

# List resources
find kustomize -type f

Files Changed

kustomize/README.md                     | 294 ++++++++++++++++++++++++++++++++
kustomize/base/gerbil-deployment.yaml   | 118 +++++++++++++
kustomize/base/kustomization.yaml       |  11 ++
kustomize/base/namespace.yaml           |   7 +
kustomize/base/pangolin-deployment.yaml |  96 +++++++++++
5 files changed, 526 insertions(+)

Production Considerations

This is an initial implementation suitable for testing and development. For production:

  • Use separate PVCs for different components
  • Configure external PostgreSQL database
  • Implement proper RBAC and network policies
  • Add monitoring with Prometheus ServiceMonitor
  • Use GitOps tools (ArgoCD, Flux) for deployment

See the comprehensive README in kustomize/README.md for production best practices.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/fosrl/pangolin/pull/2615 **Author:** [@Br1an67](https://github.com/Br1an67) **Created:** 3/7/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/issue-921-fix-921` --- ### 📝 Commits (1) - [`a0c2508`](https://github.com/fosrl/pangolin/commit/a0c2508299b97cebf3228cf8975ad5dece9cd5da) feat(kubernetes): add kustomize manifests for deployment ### 📊 Changes **5 files changed** (+526 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `kustomize/README.md` (+294 -0) ➕ `kustomize/base/gerbil-deployment.yaml` (+118 -0) ➕ `kustomize/base/kustomization.yaml` (+11 -0) ➕ `kustomize/base/namespace.yaml` (+7 -0) ➕ `kustomize/base/pangolin-deployment.yaml` (+96 -0) </details> ### 📄 Description Fixes #921 ## Community Contribution License Agreement By creating this pull request, I grant the project maintainers an unlimited, perpetual license to use, modify, and redistribute these contributions under any terms they choose, including both the AGPLv3 and the Fossorial Commercial license terms. I represent that I have the right to grant this license for all contributed content. ## Description This PR adds Kubernetes deployment manifests using kustomize, enabling users to deploy Pangolin on Kubernetes clusters. This addresses the community request for Kubernetes support as discussed in #921. The implementation includes: - **Pangolin server deployment** with health checks and resource limits - **Gerbil + Traefik deployment** using a sidecar pattern (matching the docker-compose architecture where traefik shares gerbil's network namespace) - **Persistent storage** for configuration and data - **LoadBalancer service** for external access (WireGuard ports + HTTP/HTTPS) - **Comprehensive documentation** with deployment guides and troubleshooting tips ### Architecture The deployment follows the docker-compose structure: 1. **Pangolin** - Main application server (port 3001) 2. **Gerbil + Traefik** - Combined pod with sidecar pattern: - Gerbil: WireGuard VPN tunnel (ports 51820, 21820 UDP) - Traefik: Reverse proxy (ports 80, 443 TCP) - Shares network namespace like in docker-compose ### Key Features - Uses official images: `fosrl/pangolin:latest`, `fosrl/gerbil:latest`, `traefik:v3.6` - Proper capability management (NET_ADMIN, SYS_MODULE for Gerbil) - Health checks and readiness probes - Configurable resource limits - Single PVC for all config data (can be separated for production) - Kustomize-ready structure with base layer ## How to test? ### Prerequisites - Kubernetes cluster (1.24+) - kubectl configured - Persistent volume provisioner - LoadBalancer support (or use NodePort/Ingress) ### Quick Test 1. **Create namespace and deploy**: ```bash kubectl apply -k kustomize/base ``` 2. **Verify deployment**: ```bash kubectl get all -n pangolin kubectl logs -n pangolin -l app.kubernetes.io/name=pangolin ``` 3. **Check pod status**: ```bash kubectl get pods -n pangolin ``` Expected output: ``` NAME READY STATUS RESTARTS AGE pangolin-xxx-xxx 1/1 Running 0 1m gerbil-xxx-xxx 2/2 Running 0 1m ``` 4. **Verify services**: ```bash kubectl get svc -n pangolin ``` Expected services: - `pangolin` (ClusterIP on port 3001) - `gerbil` (LoadBalancer with ports 80, 443, 51820, 21820) ### Configuration Testing Before production use, you'll need to: 1. Create a config.yml based on `config/config.example.yml` 2. Set up Traefik configuration in `config/traefik/` 3. Configure database (SQLite or external PostgreSQL) See `kustomize/README.md` for detailed configuration instructions. ### Validation All YAML files have been validated for syntax: ```bash # Validate YAML syntax python3 -c "import yaml; list(yaml.safe_load_all(open('kustomize/base/pangolin-deployment.yaml')))" # List resources find kustomize -type f ``` ## Files Changed ``` kustomize/README.md | 294 ++++++++++++++++++++++++++++++++ kustomize/base/gerbil-deployment.yaml | 118 +++++++++++++ kustomize/base/kustomization.yaml | 11 ++ kustomize/base/namespace.yaml | 7 + kustomize/base/pangolin-deployment.yaml | 96 +++++++++++ 5 files changed, 526 insertions(+) ``` ## Production Considerations This is an initial implementation suitable for testing and development. For production: - Use separate PVCs for different components - Configure external PostgreSQL database - Implement proper RBAC and network policies - Add monitoring with Prometheus ServiceMonitor - Use GitOps tools (ArgoCD, Flux) for deployment See the comprehensive README in `kustomize/README.md` for production best practices. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-16 09:46:34 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#3060
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?