From 20a95da487abc3866c13349dfeec7045bd6628f6 Mon Sep 17 00:00:00 2001 From: Lemon-miaow Date: Wed, 23 Sep 2026 19:33:04 +0800 Subject: [PATCH] docs(update): the plugins note is a rebuild + registry re-mirror now, not a node re-import The felis-paper/felis-limbo jars are baked into the lobby/limbo images; with the images hosted in the in-cluster registry, the extra step is pushing the rebuilt image there (which is also what survives an image GC), not a bare containerd import. The installer re-run does both. --- cmd/felis/update.go | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/cmd/felis/update.go b/cmd/felis/update.go index e5fc10c..37222fe 100644 --- a/cmd/felis/update.go +++ b/cmd/felis/update.go @@ -24,8 +24,9 @@ const updateTimeout = 60 * time.Second // The apply side is deliberately NOT implemented in this command. Every component // here is installed by deploy/bootstrap.sh, which is idempotent, already handles the // parts that are easy to get wrong (Velocity's pinned MINOR, the atomic jar install, -// the k3s image re-import that a byte-identical StatefulSet template will not -// trigger on its own), and is the path that gets exercised on every install. A +// the image re-import + registry push that a byte-identical StatefulSet template +// will not trigger on its own), and is the path that gets exercised on every +// install. A // second installer living in this file would duplicate that policy, could drift from // it silently, and would be reachable only on a live node where a mistake takes the // proxy or the control plane down. So `felis update` reports, and hands the operator @@ -62,7 +63,7 @@ var updateTargets = []updateTarget{ { selector: "plugins", component: "felis-api", - note: "felis-velocity.jar is a host-file swap, but felis-paper.jar and felis-limbo.jar are baked into the lobby/limbo images and need a rebuild + k3s image re-import", + note: "felis-velocity.jar is a host-file swap, but felis-paper.jar and felis-limbo.jar are baked into the lobby/limbo images and need a rebuild + re-mirror into the in-cluster registry (the installer re-run does both)", command: "sudo felis setup", }, {