Repository navigation
feat(kube): backend Kubernetes phase 1 + chart Helm + wiki - #298
Merged
Merged
Conversation
- crate devforge-kube : déploiement d'images (Deployment/Service/Ingress/Secret), probes, statut, logs, stop/start/restart, rolling update, prune (server-side apply) - DEVFORGE_RUNTIME=kubernetes (Docker reste le défaut) ; routes /api/v1/kube/* (instance_admin) ; Traefik/GC/auto-update Docker désactivés en mode k8s - chart Helm deploy/helm/devforge (PVC /data, Postgres intégré ou externe, RBAC limité au namespace des apps, PodSecurity restricted) - exemple GitHub Actions build → GHCR → déploiement ; wiki Kubernetes (Talos) - tests : snapshots de manifests, test live (DEVFORGE_KUBE_IT=1)
…For (rouge sur main)
…son waitFor (rouge sur main)" This reverts commit d01ad8b.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Kubernetes — phase 1 (expérimental)
Docker reste le backend par défaut : sans
DEVFORGE_RUNTIME=kubernetes, aucun changement de comportement.Contenu
crates/kube(nouveau) : client REST minimal (SA in-cluster, server-side apply),KubeRuntime(traitImageRuntime) : Deployment (rolling update), Service, Ingress (host, TLS cert-manager optionnel), Secret d'env, probes, statut (absent/stopped/progressing/running/degraded+ raison par pod), logs (API Pod, masqués), stop/start/restart, suppression, prune Ingress/Secret, refus de toucher aux ressources non gérées. Pods durcis (PodSecurityrestricted).RuntimeBackend(crates/shared), routes/api/v1/kube/*(instance_admin, 409 en mode Docker ;renderdispo partout). En mode k8s : pas de Traefik Docker, GC Docker ni auto-update Docker (helm upgrade).deploy/helm/devforge: 1 réplica, PVC/data, Postgres intégré (StatefulSet non-root) ou externe, ServiceAccount + Role/RoleBinding limités au namespace des apps, Service, Ingress, namespace d'apps avec labels PSA.deploy/kubernetes/README.md, exemple CIdeploy/kubernetes/examples/github-actions-build-push.yml(build → GHCR → POST/kube/apps?wait=true), wikiKubernetes.md(tuto Talos) + FAQ/Home/Sidebar/Installation.Tests
cargo test -p devforge-kube -p devforge-shared -p devforge-update✅, snapshots de manifests, clippy-D warningssurdevforge-kube✅.helm lint/helm template✅ (défaut, base externe + ingress TLS, erreur attendue sans base).restricted; test livecrates/kube/tests/live_cluster.rs(DEVFORGE_KUBE_IT=1) avec le jeton du ServiceAccount du chart : deploy, rolling update, prune, stop/start/restart, logs, list, remove, refus des ressources étrangères, 403 hors namespace ✅.Hors périmètre (P2)
Build dans le cluster (Kaniko), intégration UI/projets, adaptateur Docker du trait.