Kubernetes v1.36: Admission Policies That Can't Be Deleted
… You can now guarantee that your baseline security policies can't be removed by a cluster admin, accidentally or otherwise. …
… You can now guarantee that your baseline security policies can't be removed by a cluster admin, accidentally or otherwise. …
… That policy can live in a JSON or XML file and be maintained through code review, so updates go through a formal pull request and are reviewed like any other production change. …
… However, the security problems are still there, and as a project we're increasingly unhappy with the "insecure by default" state of the feature. …
… The nodes/proxy permission is effectively a node-level superuser capability, and granting it broadly dramatically increases the blast radius of a security incident. …
… There will be no more releases for bug fixes, security patches, or any updates of any kind after the project is retired. …
… Configuring client certificate validation Lead s : Arko Dasgupta , Katarzyna Łach GEP-91: Address connection coalescing security issue This release brings updates for configuring client certificate validation, addressing a critical security vulnerability related to connection reuse. …
… Ecosystem The Kubernetes project leadership created the Security Audit Working Group to oversee the very first third-part Kubernetes security audit , in an effort to improve the overall security of the ecosystem. …
… Since that date, there have been no further releases, no bugfixes, and no updates to resolve any security vulnerabilities discovered. …
… The updates required to improve its usability would have introduced breaking changes, so it became necessary to remove it in favor of a more friendly replacement. That replacement is Pod Security Admission , which graduates to Stable with this release. …
… Since that date, there have been no further releases, no bugfixes, and no updates to resolve any security vulnerabilities discovered. …