# Version support

Which Kubernetes minors are offered, until when, what happens at the end of support, and the control-plane upgrade {{product}} makes 30 days later.

| Minor | Patch  | End of support |
| ----- | ------ | -------------- |
| 1.36  | 1.36.6 | 2027-06-28     |
| 1.37  | 1.37.2 | 2027-10-28     |

`dcloud eks versions list` (`GET /eks/api/versions`) shows the minors, their end of support and
`defaultVersion`: the minor a create without `version` gets. The create form marks it
**(recommended)**.

Deutsche Cloud supports a minor until its end of support and offers no extended support. Deutsche Cloud
may set an earlier date for an installation (for example for a security issue without a fix); the
cluster's page then shows that date, upstream's, and the reason.

## Before and at the end of support

- 90, 30 and 7 days before, and on the day, the organization's owners and admins get an email and
  the cluster's **Activity** gets a line. Only the latest notice due is sent, so a cluster created
  20 days before gets the 30-day notice, not the 90-day one as well.
- From 90 days before, the cluster's page shows a banner, and `support.state` on the cluster is
  `ending`.
- From the end of support, `support.state` is `unsupported`: the minor takes no new clusters and no
  new node groups (`400`), and clusters still on it keep running without the SLA.

## Deutsche Cloud's upgrade 30 days after the end of support

A cluster still on the minor 30 days after its end of support gets its **control plane** upgraded
by Deutsche Cloud one minor, the same way as your own upgrade, when a newer minor is offered (there is
none above 1.37 yet, so a 1.37 cluster gets no such upgrade). Node groups are not touched.

- **When:** the first Tuesday, Wednesday or Thursday at 10:00 Berlin time on or after the end of
  support plus 30 days, and never sooner than seven days after the date was announced. The
  cluster's page shows it, and `forcedUpgrade` on the cluster carries `state` (`expected`,
  `scheduled`, `running`), `to`, `at`, `canPostpone` and `blocked`.
- **Postpone once by 14 days:** see [Postpone the forced upgrade](postpone-a-forced-upgrade.md).
- **Blocked:** when the upgrade could not start (the control plane is not settled, a node group is
  more than three minors behind, or an add-on has no version for the next minor), `blocked` says
  why, and the cluster's page shows it.
- It cannot be cancelled once it runs.
- At most three such upgrades run at a time on the installation, and one per organization. They
  start only between 10:00 and 16:00 Berlin time.

Upgrading the cluster yourself before then makes it unnecessary. See
[Upgrade the control plane](upgrade-the-control-plane.md).

## Related

- [Upgrade the control plane](upgrade-the-control-plane.md)
- [Upgrade a node group](upgrade-a-node-group.md)
