Skip to content

Commit 7afa76b

Browse files
committed
docs(hack): point the comment at the code that does what it describes
The note explaining that image-cache readiness is gated at point of use pointed into hack/e2e-apps/, which holds two monitoring suites and no runner. The readiness gate it means is the rollout status wait in hack/e2e-chainsaw/_lib/talos-image-cache.sh, along with both fallbacks to the public factory; run-kubernetes.sh only calls it. Naming the caller would have left the reader one hop short of the code. Assisted-By: Claude <[email protected]> Signed-off-by: Aleksei Sviridkin <[email protected]>
1 parent 2147e12 commit 7afa76b

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

‎hack/e2e-install-cozystack.bats‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,8 +43,9 @@
4343
# hard curl retry loop and serves it locally; tenant CRs then point
4444
# spec.talos.imageFactoryURL at its Service. Deployed here (before the long
4545
# install) so the seed download overlaps the install churn — readiness is gated
46-
# at point-of-use in hack/e2e-apps/run-kubernetes.sh, which falls back to the
47-
# public factory if the mirror never becomes Available, so this can only help.
46+
# at point-of-use in hack/e2e-chainsaw/_lib/talos-image-cache.sh, called from
47+
# run-kubernetes.sh, which falls back to the public factory if the mirror never
48+
# becomes Available, so this can only help.
4849
# Best-effort: never fail the suite on the band-aid. Remove once tenant workers
4950
# no longer bulk-pull the OS image from the public internet in CI.
5051
local sid ver

0 commit comments

Comments
 (0)