Kubernetes integrationWhat it reads

What does MarshalCloud do with Kubernetes?

• CPU and memory requested and actually used, per pod, with its node, namespace and workload, so spend can be split per namespace and per team.
• Whether each node is ready, and which pods are stuck pending, with the reason.
• It posts the numbers out to MarshalCloud; nothing connects into your cluster.

Read-only is the default everywhere. A fix is drafted, priced and explained, and then waits for a person to approve it.

What MarshalCloud never does in Kubernetes

• It reads only what cost and health need: workloads, nodes and recent events. It cannot change anything you run; its one write stays inside its own namespace.
• No logs, no environment variables, no secrets and no container contents are collected or sent.
• MarshalCloud is given no credentials to your cluster. The agent connects outward with a token you can revoke, and deleting its namespace stops it.

How do you connect Kubernetes?

1. 01Add a cluster in MarshalCloud. It shows you a token once and a short Helm command.
2. 02Run the command against your cluster. It installs one namespace, a read-only service account and a small collector, and asks for the token at your terminal so it never sits on a command line or in your shell history.
3. 03Usage starts arriving shortly after. To stop it, delete the marshal namespace.

Questions about the Kubernetes integration