Plan

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

Release you run

Products you run, and their versions

Add a product

What you run it on

Platform

Step 2:Where you want to go

Release you want

How to choose the versions in between

Fewest changes As few version changes as possible, made early when that moves you off a deprecated version sooner. Defer changes As few version changes as possible, each made as late as possible, even on a deprecated version. Stay on LTS Prefer LTS versions, even at the cost of more changes. Newest available Take the newest version each release offers. Manual Nothing is filled in. You choose the version at every release yourself.

Changing this works every path out again from the version you run, replacing steps you changed by hand. Manual changes nothing.

Step 3:Your plan

SDP 26.3 to 26.7: 1 hop.

Add the products you run to see what changes at each step.

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.

Upgrade planner

1 Step 1:What you run today

2 Step 2:Where you want to go

3 Step 3:Your plan

Summary

Step 1:What you run today

Step 2:Where you want to go

Step 3:Your plan