Skip to content

Case study

How Kinexys by J.P. Morgan Makes the Right Way the Easy Way with Kyverno

Kinexys by J.P. Morgan runs Kyverno as the policy layer of its EKS-based Kubernetes platform. A small platform team uses it to validate common misconfigurations, set safe defaults, restart workloads when certificates rotate, block risky RBAC and gate Argo CD syncs to approved change windows.

Challenge

Where the platform team started

A small cloud platform team runs an EKS-based Kubernetes platform. It owns the clusters and their add-ons, platform configuration, networking, security and the Kubernetes-related infrastructure as code. Delivery is Git-driven, and workloads follow standardized patterns, a paved path.

  • Consistent security, compliance and resiliency standards across teams and clusters.
  • The biggest risk: disruption when moving from observation to enforcement.
  • Policies must be understandable and maintainable by generalist engineers.

The goals: make the right way the easy way, enforce what must be enforced and automate what can be automated, with a repeatable, scalable baseline footprint.

Solution

Four use cases, one policy engine

Use caseWhat Kyverno doesMain beneficiary
Namespace baseline and hygieneCatches common misconfigurations, sets safe defaults, and sets a baseline RBAC and network postureOperators
Certificate rotationTriggers a rolling restart when a certificate is renewedDevelopers
nodes/proxy hardeningDenies risky RBAC and verifies existing rolesSecurity
Change management gateAllows Argo CD syncs only inside an approved windowSecurity and operators

Certificate rotation. When a certificate is renewed, its Secret is updated in place. If the Secret is annotated for restart and names its workload, Kyverno’s background controller patches the pod template’s restartedAt annotation, and a rolling restart picks up the new certificate. No manual restart, and no expired certificate.

nodes/proxy hardening. A get permission on nodes/proxy looks read-only but reaches further than expected, by design upstream, so there is no CVE to wait for. One CEL ValidatingPolicy denies Roles and ClusterRoles that grant it, after Audit mode and a background scan verified existing roles. The denial message points to nodes/metrics or nodes/stats.

Change management gate. An approved change record opens a time-boxed window that closes itself. Every Argo CD sync is an update through the Kubernetes API, so Kyverno checks for an open, verified window at admission: inside it, the sync proceeds; outside it, the sync is denied with the reason. Force and replace syncs are blocked outright.

Every use case ships through Git and Argo CD, and starts in Audit.

Results

The adoption journey

StageFocus
1. PilotStandards turned into policy, in Audit
2. StandardizeA policy library, PR reviews and CI tests
3. ScaleEnforce by tier, with scoped exceptions
4. ModernizeNew policies written in CEL

The team’s new policies are already in CEL, and the rest are moving. Kyverno 1.19 is the last release that processes legacy ClusterPolicy resources, and 1.20 runs every policy on the CEL engine.

Lessons

What to do on day one

  1. Start in Audit. Reports show who would be affected before anything is enforced.
  2. The denial message is the user interface. Developers meet policy through its message, so say what to change and why.
  3. Make the paved path compliant by default. If the common Helm chart already passes every policy, most teams never see a denial.
  4. Ship policies like everything else. The same Git reviews, CI tests and Argo CD sync as any app change.

More case studies

All case studies

Want to fast-track security and compliance in your Kubernetes environment?