What loft-sh/vcluster shipped
Written by FoxPlug from the repository's own releases; not affiliated with Vcluster. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/loft-sh/vcluster; Vcluster did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of November 2, 2026
What shipped
- Service sync no longer writes an invalid load balancer status when networking.replicateServices.fromHost maps a LoadBalancer Service, because the target Service is headless and has type ClusterIP. Pull request #4155
- Release candidate v0.38.0-rc.1 was published with a changelog from v0.38.0-alpha.8 to v0.38.0-rc.1. Release
- Release candidate v0.38.0-rc.2 was published. Release
- Release candidate v0.37.7-rc.2 was published with a changelog from v0.37.7-rc.1 to v0.37.7-rc.2. Release
- CI on v0.32 now points free-disk-space at its new owner lumbroso-commons, since GitHub Actions does not follow the repository transfer for uses:. Pull request #4263
- CI on v0.34 now points free-disk-space at its new owner lumbroso-commons, since GitHub Actions does not follow the repository transfer for uses:. Pull request #4261
- CI on v0.35 now points free-disk-space at its new owner lumbroso-commons, since GitHub Actions does not follow the repository transfer for uses:. Pull request #4260
- CI on v0.36 now points free-disk-space at its new owner lumbroso-commons, since GitHub Actions does not follow the repository transfer for uses:. Pull request #4259
Why it matters
Service sync now avoids writing a load balancer status on a headless target Service, which fixes incorrect status when host LoadBalancer Services are mapped into the cluster. The v0.38.0 and v0.37.7 release candidates continue the prerelease line. Four older release branches had their CI updated so jobs no longer fail at Set up job because the free-disk-space action moved.
Changelog entry
- Fix(servicesync): avoid invalid load balancer status sync Pull request #4155
- Release v0.38.0-rc.1 Release
- Release v0.38.0-rc.2 Release
- Release v0.37.7-rc.2 Release
- Ci: point free-disk-space at its new owner lumbroso-commons (v0.32) Pull request #4263
- Ci: point free-disk-space at its new owner lumbroso-commons (v0.34) Pull request #4261
- Ci: point free-disk-space at its new owner lumbroso-commons (v0.35) Pull request #4260
- Ci: point free-disk-space at its new owner lumbroso-commons (v0.36) Pull request #4259
This week: service sync no longer writes an invalid load balancer status when a host LoadBalancer Service maps to a headless target. Also out: v0.38.0-rc.2, v0.38.0-rc.1 and v0.37.7-rc.2, plus CI fixes on v0.32, v0.34, v0.35 and v0.36 that repoint free-disk-space to its new owner
This week in vcluster: Service sync fix: when networking.replicateServices.fromHost maps a LoadBalancer Service, the target Service is headless and therefore type ClusterIP. It no longer receives an invalid load balancer status (issue 4154). Release candidates published: v0.38.0-rc.1, v0.38.0-rc.2 and v0.37.7-rc.2. CI: the free-disk-space action moved to lumbroso-commons/free-disk-space, and GitHub Actions does not follow the transfer for uses:, so jobs failed at Set up job. The reference is updated on v0.32, v0.34, v0.35 and v0.36.
Week of October 26, 2026
What shipped
- V0.37.6 was released, following the v0.37.5 line. Release
- V0.37.5 was released as a stable cut of the v0.37 line. Release
- V0.36.4 was released, containing a bump of the minimum platform version to v4.11.4. Release
- On the v0.36 branch, the minimum platform version in pkg/platform/version.go was bumped from v4.11.3 to v4.11.4. Pull request #4253
- On the v0.35 branch, the minimum platform version was bumped from v4.10.8 to v4.10.9. Pull request #4254
- On the v0.34 branch, the minimum platform version was bumped from v4.9.6 to v4.9.7. Pull request #4255
- On the v0.37 branch, the minimum platform version was bumped from v4.12.4 to v4.12.5. Pull request #4256
- On the v0.36 branch, the image maps were changed to drop Kubernetes minors below 1.35. Pull request #4252
- On the v0.35 branch, the image maps were changed to drop Kubernetes minors below 1.35. Pull request #4250
- On the v0.34 branch, the image maps were changed to drop Kubernetes minors below 1.35. Pull request #4251
Why it matters
This week brought stable releases in the v0.37 and v0.36 lines, along with matching backports across maintained branches. The minimum platform version was raised on the v0.34, v0.35, v0.36 and v0.37 branches, tying each release line to a newer platform patch. The image maps on the v0.34, v0.35 and v0.36 branches now drop Kubernetes minors below 1.35, so provisioning for those older targets is no longer resolved from those maps, and the default Kubernetes and etcd images were bumped to patched releases on those branches.
Changelog entry
- Released v0.37.6. Release
- Released v0.37.6-rc.1. Release
- Released v0.37.5. Release
- Released v0.36.4. Release
- Bumped the minimum platform version to v4.11.4 on the v0.36 branch. Pull request #4253
- Bumped the minimum platform version to v4.10.9 on the v0.35 branch. Pull request #4254
- Bumped the minimum platform version to v4.9.7 on the v0.34 branch. Pull request #4255
- Bumped the minimum platform version to v4.12.5 on the v0.37 branch. Pull request #4256
- Dropped Kubernetes minors below 1.35 from the image maps on the v0.36 branch. Pull request #4252
- Dropped Kubernetes minors below 1.35 from the image maps on the v0.35 branch. Pull request #4250
- Dropped Kubernetes minors below 1.35 from the image maps on the v0.34 branch. Pull request #4251
- Bumped the default Kubernetes and etcd images to patched releases on the v0.35 branch. Pull request #4248
V0.37.6 and v0.37.5 are out, with v0.37 and v0.36 releases this week. Minimum platform versions were bumped on the v0.34, v0.35, v0.36 and v0.37 branches, Kubernetes minors below 1.35 were dropped from the image maps on v0.34 through v0.36, and default Kubernetes and etcd images
Stable v0.37 and v0.36 releases arrived this week. Alongside them, maintenance updates landed across the v0.34, v0.35, v0.36 and v0.37 branches. The minimum platform version was bumped on each of those branches, moving to v4.9.7, v4.10.9, v4.11.4 and v4.12.5 respectively. The image maps on the v0.34, v0.35 and v0.36 branches now drop Kubernetes minors below 1.35, which means clusters still targeting older minors will no longer get images resolved from those maps. The same branches also bumped the default Kubernetes and etcd images to patched releases.
Week of October 19, 2026
What shipped
- Released v0.37.4 as a stable patch release. Release
- Bumped the default Kubernetes images on v0.35 to patched releases including v1.36.5, v1.35.9 and v1.34.12 to address CVE-2026-2270 in kube-controller-manager. Pull request #4189
- Bumped the default Kubernetes images on v0.36 to the same patched releases, covering the kube-controller-manager CVE. Pull request #4188
- Bumped the default Kubernetes images on v0.34 to v1.35.9 and matching patches, since that line has no 1.36 entry. Pull request #4190
- Fixed snapshot restore for embedded databases on v0.36 so the kine revision bump is kept. Pull request #4234
- Removed string-form controlPlane.distro.k8s.image handling from pinKubernetesVersion in the docker driver on v0.34. Pull request #4215
- Removed the same string-form image tag handling from the docker driver on v0.35. Pull request #4216
- Removed the same string-form image tag handling from the docker driver on v0.36. Pull request #4217
- Changed CI on v0.34 to authenticate private Go modules with a credential helper, backported to v0.35 and v0.36. Pull request #4228
- Raised the minimum vCluster Platform version for the v0.34 line from v4.9.5 to v4.9.6. Pull request #4210
Why it matters
This week focused on patched default Kubernetes images across the v0.34, v0.35 and v0.36 lines, which matters if you rely on the shipped defaults. The snapshot fix on v0.36 keeps the kine revision bump on embedded database restore, and the docker driver lost string-form image tag handling that only existed in backports. Release candidates and alphas also moved through v0.37.4 and v0.38.0.
Changelog entry
- Released v0.37.4. Release
- Published v0.37.4-rc.3 as a release candidate. Release
- Published v0.37.4-rc.2 as a release candidate. Release
- Published v0.37.4-rc.4 as a release candidate. Release
- Published v0.38.0-alpha.5. Release
- Published v0.38.0-alpha.6. Release
- Published v0.38.0-alpha.7. Release
- Bumped Go to 1.26.10 on v0.34 as a release candidate backport. Release
- Bumped default Kubernetes images on v0.35 to v1.36.5, v1.35.9 and v1.34.12 for CVE-2026-2270. Pull request #4189
- Bumped default Kubernetes images on v0.36 to v1.36.5, v1.35.9 and v1.34.12 for CVE-2026-2270. Pull request #4188
- Bumped default Kubernetes images on v0.34 to patched releases including v1.35.9. Pull request #4190
- Raised the minimum Platform version for v0.34 to v4.9.6. Pull request #4210
This week: v0.37.4 released. Default Kubernetes images bumped to patched releases on v0.34, v0.35 and v0.36 for CVE-2026-2270. Snapshot restore on v0.36 now keeps the kine revision bump, and the docker driver drops string-form image tag handling.
This week's changes span patched Kubernetes images, snapshot restore correctness and CLI cleanup. The default Kubernetes images on v0.34, v0.35 and v0.36 now point at patched releases covering CVE-2026-2270 in kube-controller-manager. On v0.36, restoring an embedded database keeps the kine revision bump. The docker driver no longer handles the string-form controlPlane.distro.k8s.image setting on the v0.34, v0.35 and v0.36 backports, since that legacy path never existed on main. CI on v0.34 now authenticates private Go modules with a credential helper, also backported to v0.35 and v0.36, and the minimum Platform version for v0.34 moved from v4.9.5 to v4.9.6. v0.37.4 shipped as a stable release.
Week of October 5, 2026
What shipped
- Fixed the syncer so unsynced changes are kept when a sync fails part way. Pull request #4200
- Fixed the proxy to send the upstream host to the API server. Pull request #4198
- Released v0.38.0-alpha.2. Release
- Released v0.38.0-alpha.1. Release
- Released v0.37.3. Release
- Released v0.37.3-rc.2. Release
Why it matters
This week includes fixes for the syncer and proxy, making sync more reliable and API server requests correct. It also brings new alpha and patch releases for users to try.
Changelog entry
- Release v0.38.0-alpha.2. Release
- Release v0.38.0-alpha.1. Release
- Release v0.37.3. Release
- Release v0.37.3-rc.2. Release
- Fixed syncer to keep unsynced changes when a sync fails part way. Pull request #4200
- Fixed proxy to send upstream host to the API server. Pull request #4198
V0.38.0-alpha.2 and v0.37.3 are out this week. We fixed the syncer to keep unsynced changes when a sync fails part way, and fixed the proxy to send the upstream host to the API server.
This week we shipped v0.38.0-alpha.2, v0.38.0-alpha.1, v0.37.3, and v0.37.3-rc.2. We fixed the syncer so that unsynced changes are kept when a sync fails part way, preventing loss of virtual changes. We also fixed the proxy to send the upstream host to the API server, ensuring correct Host and:authority headers. These changes improve reliability for users running virtual clusters.
Week of September 21, 2026
What shipped
- V0.37.2 released with updates from the v0.37 branch. Release
- V0.36.3-rc.1 released with ServiceMonitor scrape interval configuration and codeowners refactoring. Release
- Nine pending v0.37 commits replayed from vcluster-pro to bring the OSS branch up to date. Pull request #4183
Why it matters
The project released maintenance updates across two minor versions while syncing pending changes from the pro repository. ServiceMonitor scrape interval is now configurable in v0.36, improving monitoring flexibility.
Changelog entry
- Feat(chart): make ServiceMonitor scrape interval configurable Release
- Chore: refactor codeowners Release
- Replayed nine commits from vcluster-pro v0.37 branch to OSS v0.37 Pull request #4183
Vcluster v0.37.2 and v0.36.3-rc.1 are available. ServiceMonitor scrape intervals are now configurable, and v0.37 branch is synced with pending changes.
New releases for Vcluster: v0.37.2 is now available with the latest updates, while v0.36.3-rc.1 brings configurable ServiceMonitor scrape intervals. The v0.37 branch has been synced with nine previously pending commits from vcluster-pro, keeping the OSS repository current with upstream changes.
Week of September 14, 2026
What shipped
- V0.37.1 released. Release
- V0.37.1-rc.3 released. Release
- V0.37.1-rc.2 released. Release
- Codeowners metadata refactored in v0.36 OSS branch. Pull request #4182
- Codeowners metadata refactored in v0.35 OSS branch. Pull request #4180
- Codeowners metadata refactored in v0.34 OSS branch with merge conflict resolution needed. Pull request #4181
Why it matters
V0.37.1 is now available with release candidate builds leading up to it. Codeowners changes were applied across multiple stable branches to keep review ownership metadata current across versions.
Changelog entry
Vcluster v0.37.1 is out. Check the changelog for what's included in this release.
Vcluster v0.37.1 is now available. This release follows three release candidates (rc.2 and rc.3) and includes updates to review ownership across supported branches. Upgrade when ready and refer to the full changelog for details.