Kubernetes integration. Find out why pods crash, get OOM-killed or never become ready.
Praxen Inc. maps your cluster with a read-only agent, investigates crashloops, OOM kills and stuck rollouts from logs and events, and fixes code or manifests.
Why Praxen Inc. for Kubernetes
Get started for freeHow to set up Kubernetes
The product guide says cluster registration usually takes under a minute after installation. Initial workload discovery follows registration.
- Start the Kubernetes connection in Praxen Inc. The flow creates a Praxen Inc. API key scoped to cloud_accounts:write.
- Run the displayed Helm install command for oci://ghcr.io/coreplanelabs/charts/praxen-k8s in the praxen namespace with your cluster name and API key. For production, use apiKey.existingSecret instead of putting the key on the command line.
- Check the registered cluster in Praxen Inc. If it does not appear, inspect the agent pod and its logs in the praxen namespace.
Permissions and access
The agent uses read-only Kubernetes RBAC: get, list and watch. It registers once with the cloud_accounts:write Praxen Inc. key and establishes an outbound Cloudflare Tunnel; cluster credentials stay inside the cluster. The documented agent flow has no full-access mode. A complete resource-by-resource Helm RBAC manifest was not available in the checked product sources; review the chart before installation.
Discovery, refresh and the connected view
Cluster inventory sync is scheduled every 15 minutes, separately from the three-minute agent liveness probe. Namespaces, nodes, workloads, pods, services, ingress, volumes and policy resources appear in the graph. The kubectl investigation tool makes read-only calls through the agent rather than requiring a public Kubernetes API endpoint.
Disconnect and revoke access
Run helm uninstall praxen --namespace praxen, disconnect the cluster in Praxen Inc., and revoke the agent API key under Settings → API keys. Disconnecting also tears down the managed tunnel.
Provider credentials and Praxen Inc.’s access mode are separate. Where write-capable tools exist, the connected account’s Settings page offers a Read-only switch. Turning it off permits writes subject to review and confirmation, but cannot add permissions to the provider credential. Agent-connected Kubernetes clusters stay read-only.
In the graph.
Every Kubernetes resource Praxen Inc. picks up sits in the graph with its connections, config and history.
Namespace Node Deployment Stateful Set Daemon Set Replica Set Job Cron Job Pod Service Ingress Config Map Secret Service Account Role Role Binding Cluster Role Cluster Role Binding Persistent Volume Persistent Volume Claim Storage Class Network Policy Horizontal Pod Autoscaler Pod Disruption Budget Kubernetes tools.
The calls Praxen Inc. can make to Kubernetes when it looks into an issue.
Kubernetes -
kubectlRead and operate on Kubernetes resources on a connected cluster (get/list/describe/logs/events/top/rollout, plus scale, restart, patch, delete, apply)
Kubernetes setup and troubleshooting
Common questions.
How does Praxen Inc. connect to my Kubernetes cluster?
Start the Kubernetes connection in Praxen Inc. The flow creates a Praxen Inc. API key scoped to cloud_accounts:write. Run the displayed Helm install command for oci://ghcr.io/coreplanelabs/charts/praxen-k8s in the praxen namespace with your cluster name and API key. For production, use apiKey.existingSecret instead of putting the key on the command line. Check the registered cluster in Praxen Inc. If it does not appear, inspect the agent pod and its logs in the praxen namespace.
What Kubernetes resources does Praxen Inc. sync?
Cluster inventory sync is scheduled every 15 minutes, separately from the three-minute agent liveness probe. Namespaces, nodes, workloads, pods, services, ingress, volumes and policy resources appear in the graph. The kubectl investigation tool makes read-only calls through the agent rather than requiring a public Kubernetes API endpoint.