Manufacturing and energy / Head of Infrastructure / Before / after

The plant does not stop for a Kubernetes upgrade

Two cloud engineers, one factory, and the CrashLoopBackOff that used to mean overtime.

Published September 12, 2026/01 / 06

Manufacturing IT is two cloud engineers supporting systems the plant depends on, next to OT nobody is allowed to touch. When a pod goes CrashLoopBackOff during a production run, there is no bench to escalate to. There is overtime.

Before: the K8s estate runs on borrowed expertise, upgrades are scheduled around fear, and the peak-season crash loop takes an afternoon of two people’s time the plant cannot spare. After: agents run the investigation the moment the loop starts, the fix is drafted with the evidence attached, and one engineer approves it between other work.

MSM anchors the proof across a multi-cloud and Kubernetes estate: tooling cost down 63% after consolidating onto CloudThinker. Borrowed for the vertical, named as such; the K8s loop is identical.

#AISRE #Manufacturing #Resolve #CloudThinker

02 / 06 The problem

Two engineers, one plant, zero slack

The team

Two people

Cloud, K8s, networking, vendor systems and the ERP integration. Both of them.

The moment

CrashLoopBackOff at peak

A scheduling service pod loops during the quarter’s biggest production run.

The afternoon

Everything else stops

Both engineers drop their work. Logs, describes, events, a rollback theory, four hours gone.

4 hours

of two-person time per serious K8s incident, taken from a team of two.

0

specialists on the bench. Escalation means a consultant and a purchase order.

The plant tolerates no downtime, and the team has no redundancy. Something has to give.

03 / 06 Why the current answers fail

Two ways to fail: keep doing it by hand, or hand production to an agent on day one

Option A: the status quo

  • One-off scripts

    one per account, none the same

  • Tribal knowledge

    the standard lives in someone’s head

  • Manual follow-up

    tickets chased, dashboards watched

  • Quarterly evidence

    compliant in audit week, unknown after

Resultsafe, does not scale

Option B: AI with full access

  • Trust on a promise

    a demo is not a control

  • Unscoped credentials

    one key for cloud and on-prem alike

  • Recommendations only

    still a human acts, still no evidence

  • No audit trail

    the regulator asks; the chat log answers

Resultscales, nobody signs off

What the manufacturing teams we work with chose

Neither. The K8s loop runs through agents: detect, investigate, draft. The two engineers keep the gate, and their afternoons.

Trust is not granted to a system. It is earned, one audited check at a time.

04 / 06 Frontier Investigation Agents

Four steps from read-only to autonomous. The team decides when to take each one.

Step 1

Verify

Read only

Live inventory, drift, waste and health checks. Nothing changes. Every finding explains what was checked, what was found, why it matters.

Step 2

Encode

Standards as Skills

Naming, tagging, guardrails, cost controls and runbooks written once and run the same way in every account. Tribal knowledge becomes a file.

Step 3

The gate

Act with approval

Agents investigate and propose. A person approves where risk, policy or production impact demands it. Every action is written to the audit trail.

Step 4

Auto mode

Autonomous under guardrails

Per environment, the team sets Notify, Act-with-Approval or Autonomous. Low-risk remediations run on their own. Production keeps the gate.

The infra lead’s question

“We cannot risk the OT side. How is that enforced?”

Scope is structural: the agents hold brokered credentials only for the systems you connect. The OT network is not connected, so it is not reachable, and the audit log proves it.

Frontier Investigation Agents for your cloud. They scale the team’s judgment, they do not replace it.

05 / 06 Proof

The same crash loop, after

T+0 min

Loop detected

Pod restart pattern flagged; investigation opens with events, logs and the last config change.

T+6 min

Cause named

A resource limit regression from the morning’s manifest change, evidence attached.

T+9 min

Fix approved

One engineer reviews the drafted patch and taps approve without leaving their other work.

A separate tool for every job

-63%

tooling cost after consolidating onto CloudThinker.

The upgrade stopped being scheduled around fear.

06 / 06 One number, and the ask

The only number we ask you to check yourself

Read-only, first 30 days

Zero changes to production

Start the way our customers did. One scoped, read-only key. The engine inventories your estate and reports drift, waste and health. Your team checks the findings against what it already knows. If they hold, you decide the next step.

What you get

1 report

Full inventory, drift and waste findings, each with what was checked and why it matters.

What you risk

1 read key

Scoped and revocable. Every check it runs is in the audit log from day one.

Do not trust the AI. Verify it. Then let it earn the next step.

Sources

The evidence

MSM

Tooling cost down 63% after consolidating onto CloudThinker, multi-cloud plus K8s.

Read the full evidence

The module

Resolve

The part of CloudThinker this story runs on, in product terms.

Explore Resolve
Read-only, first 30 days

Start a read-only pilot

One scoped, revocable read key. One report on inventory, drift, waste and health. Zero changes to production. Your team judges whether the findings hold.