change how we sync metallb #160
jessebot
commented
Owner
- metallb default points to git.open.engineering as the base repo for the smol-app
- do a final bump to sync-wave 3
- metallb default points to git.open.engineering as the base repo for the smol-app
- do a final bump to sync-wave 3
jessebot
added the patch
label
jessebot
self-assigned this
jessebot
added 1 commit 2026-11-10 18:37:06 +00:00
change how we sync metallb
Some checks failed
Test smol-k8s-lab / test_k3s (pull_request) Failing after 2m43s
Details
jessebot
added 2 commits 2026-11-10 18:41:42 +00:00
update git.open.engineering
159426bfdd
update docs to match
All checks were successful
Test smol-k8s-lab / test_k3s (pull_request) Successful in 7m28s
Details
jessebot
merged commit 14ac6f6b5d into main
jessebot
deleted branch metallb-updates
jessebot
referenced this pull request from a commit
change how we sync metallb (#160)
No reviewers
Labels
No labels
TUI
bug
docs
duplicate
enhancement
help wanted
invalid
major
question
secrets
wontfix
Security
Storage
blocked
bug
docs
duplicate
enhancement
help wanted
invalid
major
minor
networking
patch
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
oeng/smol-k8s-lab!160
Loading…
Reference in a new issue
No description provided.
Delete branch "metallb-updates"
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?