| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2026-09-14 | 2.7 kB | |
| v1.76.14 Deckhouse Kubernetes Platform source code.tar.gz | 2026-09-14 | 236.2 MB | |
| v1.76.14 Deckhouse Kubernetes Platform source code.zip | 2026-09-14 | 247.0 MB | |
| Totals: 3 Items | 483.2 MB | 4 | |
Changelog v1.76.14
Know before update
- During the first
user-authzrelease after the update the per-role bindings are protected from the release engine, the aggregated ones are created, and the per-role bindings are deleted right after the release. Permissions granted through annotated ClusterRoles stay in place throughout. Theuser-authz.deckhouse.io/access-levellabel is now set automatically on annotated ClusterRoles. In audit logs, access granted through annotated ClusterRoles is attributed touser-authz:<level>:custominstead of the individual ClusterRole.
Fixes
- [service-with-healthchecks] Fixed a load balancer losing all its endpoints for good after a target pod was replaced. #22980
The
service-with-healthcheckscontroller and agent are restarted. AServiceWithHealthchecksthat was left inNotAllEndpointsAreReadywith no EndpointSlice recovers automatically once the updated agent starts, no manual action is needed. - [user-authn] Fixed DexAuthenticator pod creation under ResourceQuota by setting init container CPU/memory limits to the sum of main container limits. #22998
- [user-authz] Grant custom ClusterRoles (annotated with
user-authz.deckhouse.io/access-level) through one aggregated ClusterRole per access level, so the number of bindings per ClusterAuthorizationRule/AuthorizationRule no longer depends on the number of such roles. #22968 During the firstuser-authzrelease after the update the per-role bindings are protected from the release engine, the aggregated ones are created, and the per-role bindings are deleted right after the release. Permissions granted through annotated ClusterRoles stay in place throughout. Theuser-authz.deckhouse.io/access-levellabel is now set automatically on annotated ClusterRoles. In audit logs, access granted through annotated ClusterRoles is attributed touser-authz:<level>:custominstead of the individual ClusterRole. - [user-authz] Group the module alerts under a group named apart from the alerts themselves, so the incident shelf accepts them. #22999