alvis/oO
1
0
Fork 0
Code Issues 34 Pull Requests Actions Packages Projects Releases Wiki Activity

k3s intermediate stop on the path to full k8s #60

New Issue
Open
opened 2026-04-13 14:35:37 +00:00 by alvis · 0 comments
alvis commented 2026-04-13 14:35:37 +00:00
Owner
Copy Link

Before Phase-5 full k8s, introduce k3s on the existing VM to remove the 'compose → k8s' cliff. Helm charts target both. Ingress via Caddy or Traefik. When multi-node is justified, promote to k8s; manifests are already compatible.

Before Phase-5 full k8s, introduce k3s on the existing VM to remove the 'compose → k8s' cliff. Helm charts target both. Ingress via Caddy or Traefik. When multi-node is justified, promote to k8s; manifests are already compatible.
alvis added this to the M5 — Production hardening milestone 2026-04-13 14:35:37 +00:00
alvis added the infra label 2026-04-13 14:35:37 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
admin
backend
design
good-first-issue
infra
ml
mobile
platform
web
No Label infra
Milestone
No items
No Milestone M5 — Production hardening
Projects
Clear projects
No project
Assignees
Clear assignees
alvis
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: alvis/oO#60
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?