Upgrade planner
An SDP upgrade goes through every release in between, and each release ships several versions of every product. Tell the planner where you are and where you want to land, and it works out every release you pass through and which product versions change at each one.
Step 1:What you run today
Step 2:Where you want to go
Step 3:Your plan
Summary
SDP 26.3 to 26.7: 1 hop.
Provisional until every product has a version at every release.
Steps to follow
Upgrading the operators, at every step
Upgraded operators restart your stacklets on new images, so each step replaces them with reconciliation paused:
- Pause reconciliation of every stacklet: set
spec.clusterOperation.reconciliationPaused: true. - Upgrade the operators, following the release's upgrade steps.
- Check the release's notes for breaking changes and manual steps, such as CRD updates or product upgrade guides.
- Resume reconciliation one stacklet at a time: set
reconciliationPausedback tofalseand let it restart on the new images before resuming the next.
SDP 26.3 to 26.7
Operators
Upgrade all operators to SDP 26.7 using the steps above.
Follow the upgrade steps and the SDP 26.7 release notes.
Versions at each release
Each column is an SDP release, and each box a product version that release ships. Change any step by choosing another version; only versions the step before can reach are offered.
This plan is generated from the release metadata the hub holds. Read it alongside the SDP release notes, which carry the breaking changes and the supported Kubernetes versions for each release.