Release Channels Foundry 1.6+
In order to keep Kubernetes up to date, you specify two things:
- The Kubernetes minor version
- Which release channel to follow (how soon to apply patch releases that meltcloud publishes for it)
Both are selected individually for Clusters, Machine Pools and Elastic Node Pools.
Kubernetes Bundles
meltcloud ships Kubernetes Bundles, e.g. 1.35.5-melt.30: a Kubernetes patch version together with the meltcloud components built for it (such as OS Image/Flatcar version, CNI, Ingress Controller).
Following a Release Channel
| Name | Update speed | Risk appetite |
|---|---|---|
fast | Receives new patch releases first | High: Early-adopting enterprises |
regular | Receives patch releases once they have proven themselves on fast | Medium: typical enterprise environments |
stable | Receives patch releases last, once they have proven themselves on regular | Low: slow-moving enterprise environments |
manual | Receives no updates; you pin a specific Kubernetes Bundle | You decide: see Pinning a Kubernetes Bundle |
A Cluster or Pool that follows a Release Channel runs the newest Kubernetes Bundle the channel has for its Kubernetes minor version. When a newer bundle is published, meltcloud automatically prepares a new revision, which is rolled out via Maintenance Schedule or manually.
Pinning a Kubernetes Bundle
Choose the Release Channel manual to pin a specific Kubernetes Bundle under Pinned Version. A pinned Cluster or Pool does not receive updates until you pin another bundle or follow a channel again.
WARNING
Pinning a bundle means stopping security patches. Do it only for as long as you need to, e.g. to hold back an update while you investigate an issue.