New control planes in Upbound Spaces now default to UXP v2

Last updated: April 9, 2026

New managed control planes in Upbound Spaces will default to Upbound Crossplane (UXP) v2 when you do not specify a Crossplane version. Existing control planes are not affected — release channels never cross major version boundaries automatically.

What is changing

  • New control planes without a version set now get the latest stable UXP v2 on the Stable channel, instead of v1.

  • New control planes with an explicit version are unchanged.

  • Existing control planes on v1 are unchanged.

What you need to do

  • You want new control planes on v2 (recommended): No action required. Create control planes as you do today; the default is now v2.

  • You need new control planes to stay on v1: Set the Crossplane version to a supported 1.x release when you create the ControlPlane (for example, 1.20.5-up.1). Spaces will keep that control plane on v1 and only offer v1 patch upgrades.

  • You already pin a specific version: No change in behavior. The new default only applies when the version field is omitted.

FAQ

Will my existing v1 control plane be upgraded to v2?

No. Channels only deliver updates within the same major version. A v1 control plane stays on v1 until you explicitly set a v2 version.

Can I move an existing v1 control plane to v2?

Yes. Set the Crossplane version to a supported 2.x release. See the Crossplane v2 upgrade guide for what to review before upgrading.

Note: in order to upgrade to v2 you must be on 1.20 first, and upgrade one minor version at a time.

What changed in UXP v2?

UXP v2 aligns with Crossplane v2, which includes new capabilities and removes some deprecated features. See removed and changed features in v2 for details.

Why are we changing the default?

UXP v2 is our recommended path for new deployments. Defaulting to v2 ensures new control planes start on the latest supported platform without requiring a v1 to v2 upgrade.