Skip to content

Add k3s deployment mode — lightweight alternative to k8s for small/medium enterprises#324

Open
riverfor wants to merge 4 commits intoiflytek:mainfrom
riverfor:main
Open

Add k3s deployment mode — lightweight alternative to k8s for small/medium enterprises#324
riverfor wants to merge 4 commits intoiflytek:mainfrom
riverfor:main

Conversation

@riverfor
Copy link
Copy Markdown

@riverfor riverfor commented Apr 17, 2026

Summary

A new and simple deployment mode has been added: deployment under k3s, suitable for small and medium-sized enterprises.
Compared to k8s, k3s requires fewer resources.

Validation

No code was changed; the following tests should be unnecessary. I successfully deployed and conducted simple tests on my local k3s cluster.

  • Backend tests passed
  • Frontend typecheck/build passed
  • OpenAPI SDK regenerated or checked when API contracts changed
  • Smoke test run when relevant

Commands run:

kubectl apply -k deploy/k3s/overlays/quickstart/

Risk

None

Notes

Add self-contained K3s deployment configuration under deploy/k3s/:
- quickstart overlay with PostgreSQL, Redis, backend, frontend, scanner
- Kustomize-based single-command deployment (kubectl apply -k)
- Traefik-compatible Ingress (no nginx ingressClassName)
- Built-in defaults for local testing with skillhub.local
- Remove OAuth2 env vars from backend-deployment to fix empty-client-id crash
Add a K3s subsection under Kubernetes in both README.md
and README_zh.md with a one-line deploy command and link
to the full k3s README.
@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Apr 17, 2026

CLA assistant check
All committers have signed the CLA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants