Join our Newsletter — 33% off our NHI Course

What would it take for ModelKit to cover provenance and policy?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20217
Topic starter  

TL;DR: Provenance, not model code alone, is the hardest gap in Kubernetes AI stacks, Jozu found, because teams cannot reliably prove what is running, how it was approved, or how to roll it back. Model provenance has to anchor packaging and admission decisions before the rest of the stack can be governed.

Editorial analysis by NHI Mgmt Group, based on content published by Jozu: “Open Source Kubernetes Solutions for Enterprise AI: A Practical Map”.

Key questions

Q: Why does AI governance depend on signed provenance as much as cluster policy?

A: Cluster policy can only enforce rules on what it can recognise, so it cannot replace trust in the underlying artefact.

Q: How should security teams govern AI in the security stack?

A: Security teams should treat AI as a governed decision aid, not an autonomous authority.

Q: What breaks when AI model evaluations are not versioned?

A: Without versioned datasets and prompts, score changes become hard to trust because the difference may come from the test setup rather than the model.

Practitioner guidance

  • Map the AI stack as one governed lifecycle Document where notebooks, training jobs, schedulers, serving endpoints, registries and policy decisions live, then assign an owner for each transition between them.
  • Package models as versioned artefacts before promotion Require the model, datasets, code, prompts and configuration to move together as a single approved unit so lineage and rollback stay intact.
  • Bind deployment approval to signed provenance Use signature verification on OCI-stored model artefacts and refuse promotion when provenance, attestation or ownership cannot be verified.

Bottom line: The article’s central point is that enterprise AI on Kubernetes is usually a stitched-together stack, so governance has to span development, scheduling, serving, packaging and policy.

Glossary terms: ModelKit, Model Provenance, Admission Controller, Workload Identity

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20707
 

Open source AI governance fails first at the seams, not in the model itself. The article shows that enterprises rarely run a single platform, so control is distributed across orchestration, scheduling, serving, packaging and policy. That creates a governance seam where ownership can be lost between teams, especially when identity, signing and approval are handled outside the AI stack. The practical conclusion is that the control objective is lifecycle coherence, not tool consolidation.

A few things that frame the scale:

  • AI-related credential leaks surged 81.5% year-over-year in 2025, with the surrounding AI infrastructure leaking 5x faster than core LLM providers, according to the State of Secrets Sprawl 2026.
  • Enterprise AI use rose from 55% of organisations in 2023 to 88% in 2025, according to McKinsey’s Global Surveys on the State of AI.

A question worth separating out:

Q: Should organisations prioritise model packaging before adding more serving tools?

A: Yes, when the organisation cannot reliably answer which model version is in production or how its dependencies were approved. Packaging fixes the traceability problem first, which makes later serving, scheduling and policy decisions meaningful. Adding more serving layers before provenance is in place usually increases speed without improving governance.

👉 Read our full editorial: Open source Kubernetes AI stacks need packaging and policy


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.