Unavailable platform tools or resources

Establish the agent environment

Confirm where the agent runs: inside a game JVM, directly on a host, or inside a container. Check the operating-system user and available tools in that environment.

A host-installed CLI is not automatically available inside the agent container. A mounted socket does not also mount host scripts, user-service files, or kubeconfig credentials.

Docker

Check the daemon socket, its permissions, and Docker capability. Compare the inventory with the same daemon using the native CLI. Compose actions need a Compose CLI accessible to the agent.

Podman

Check the native Libpod API socket and user scope. Rootless Podman resources belong to one user. Compare with that user's native inventory.

Quadlet needs Linux and systemd access. Buildah needs its CLI and local store. Podman kube actions need the Podman CLI. Check Podman installation for the distinction between API access and host tooling.

Kubernetes

• Forbidden: identify the exact denied verb, resource, namespace, and subresource. Review the service account's RBAC.
• Missing metrics: check the Kubernetes metrics API.
• Missing Helm actions: check the Helm CLI in the agent environment.
• Missing drain or maintenance actions: check kubectl and its applicable access.
• Authentication failure: confirm the supported kubeconfig or in-cluster credentials and custom CA.

Native targets have different TLS and credential support from JVM targets. Read container platforms before choosing a credential mechanism.

YAML comparison runs through native API discovery and dry-run logic. Installing kubectl alone will not fix missing read or dry-run permissions.

Verify the fix

Retry a small inventory read before attempting a write. Check a fresh result from the intended daemon or cluster, then repeat the original action with valid input.

If all live reads fail, use live connection troubleshooting.