Skip to content

docs: add procedures for disabling loopback workaround #153

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 1, 2025
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
48 changes: 48 additions & 0 deletions docs/install-upgrade/upgrade.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,53 @@
# Upgrade

## Upgrades removing loopback connections
Starting with Fabric 25.03 and Broadcom SONiC 4.5.0, loopback connections are no longer
required for local VPC peering. A feature flag has been created to assist in a
smooth removal process, `loopbackWorkaroundDisable`, which takes a boolean
value.

### Fresh installs of 25.03

Users in a greenfield environment installing version 25.03 of the Fabric will
see that `hhfab init` will supply the needed option. For users who are
generating configuration in another way ensure that
`loopbackWorkaroundDisable: true` is inside `.spec.config.fabric` of the
Fabricator object.


### Upgrades to 25.03

For users upgrading to version 25.03 follow the steps:

0. Upgrade to 25.03 using steps from [previous
versions](#upgrades-from-beta-1-onwards)

0. Ensure all switch agents are on v0.80.0 (or greater)
* `kubectl get agents` to see the version

0. Upgrade the switch operating systems to 4.5.0
* the switch reinstall feature of k9s is very useful for this purpose

0. Confirm all the switches are up and running SONiC 4.5.0
* `kubectl get agents -o wide`, look at the Software column

0. Run the command to patch the fabricator object
* `kubectl patch -n fab --type merge fabricator/default -p '{"spec":{"config":{"fabric":{"loopbackWorkaroundDisable":true}}}}'`

0. Ensure that all agents have converged:
* `kubectl get agents -o wide`, ensure that columns `currentg` equals `appliedg`

0. Now the loopback connections can be removed from the logical wiring:
* `kubectl get connections | grep loopback`
* `kubectl delete connections/leaf-03--vpc-loopback`
0. Finally, unplug loopback cables as needed


### Beyond 25.03
Starting in 25.04 the presence of `loopbackWorkaroundDisable: true` will be required
in order for updates to take place.


## Upgrades from Beta-1 onwards

Starting with Beta-1 release and onwards, the upgrade process is more streamlined and fully automated. The control node
Expand Down