| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2026-10-22 | 3.9 kB | |
| v1.77.4 source code.tar.gz | 2026-10-22 | 166.9 MB | |
| v1.77.4 source code.zip | 2026-10-22 | 176.4 MB | |
| Totals: 3 Items | 343.2 MB | 0 | |
Changelog v1.77.4
Know before update
- Cilium agent and operator pods will be restarted.
- CoreDNS pods will be restarted.
- NodeGroups that already have preemptible: true under the CAPI engine keep their current regular VMs until the next rollout (any rollout-triggering InstanceClass change or manual-rollout-id); after that rollout their nodes become preemptible VMs and are rotated every ~20h.
- Upgrade does not recreate any node. NodeGroups that already have preemptible: true under the CAPI engine keep their current regular VMs; Machines created after the upgrade (scale-up, replacement) are preemptible, so such NodeGroups run mixed VMs until a full rollout (any rollout-triggering InstanceClass change or the manual-rollout-id annotation). Preemptible VMs are rotated every ~20h.
- metallb pods will be restarted.
- node-local-dns pods will be restarted.
Fixes
- [cilium-hubble] Fixed known vulnerabilities in the Hubble relay and UI images. #713
- [cloud-provider-dvp] A DVP cluster migrated to the new provider configuration format keeps its
networkPolicy - Noneinstead of silently switching toIsolated. #845 - [cloud-provider-dvp] Clusters with
networkPolicy - Nonein the provider configuration no longer get NetworkPolicies created for LoadBalancer Services. #859 - [cloud-provider-yandex] Preemptible nodes are created as preemptible VMs and rotated before the 24h limit when a NodeGroup is managed by the CAPI engine. #76 NodeGroups that already have preemptible: true under the CAPI engine keep their current regular VMs until the next rollout (any rollout-triggering InstanceClass change or manual-rollout-id); after that rollout their nodes become preemptible VMs and are rotated every ~20h.
- [cloud-provider-yandex] Preemptible nodes are created as preemptible VMs and rotated before the 24h limit when a NodeGroup is managed by the CAPI engine. #771 Upgrade does not recreate any node. NodeGroups that already have preemptible: true under the CAPI engine keep their current regular VMs; Machines created after the upgrade (scale-up, replacement) are preemptible, so such NodeGroups run mixed VMs until a full rollout (any rollout-triggering InstanceClass change or the manual-rollout-id annotation). Preemptible VMs are rotated every ~20h.
- [cni-cilium] Fixed known vulnerabilities in the Cilium images. #713 Cilium agent and operator pods will be restarted.
- [common] Fixed known vulnerabilities in the CNI migration images. #715
- [deckhouse] Bump containerd to v2.2.10 and dependencies to fix CVEs #821
- [kube-dns] Fixed known vulnerabilities in the CoreDNS and sts-pods-hosts-appender images. #714 CoreDNS pods will be restarted.
- [metallb] Fixed known vulnerabilities in the MetalLB images. #719 metallb pods will be restarted.
- [node-local-dns] Fixed known vulnerabilities in the node-local-dns images. #714 node-local-dns pods will be restarted.
- [registrypackages] Fixed known vulnerabilities in the kubernetes-cni package. #721