On-Prem Platform
This part of the documentation is only intended in the context of a supported PoC (Proof of Concept) together with the Steadybit team. Please, book an appointment to scope your PoC before continuing to evaluate the on-prem solution.
This page describes some common issues and how to solve them.
- Check the logs of the platform and Postgres containers
kubectl logs -f -n steadybit-platform steadybit-platform-postgresql-0 --previous
kubectl logs -f -n steadybit-platform steadybit-platform-0 --previous
- Verify that the Postgres password is correct and base64 encoded in the manifest file
- Check the logs of the agents
kubectl logs -f -n steadybit-agent steadybit-agent-0
- If you see this error:
Missing permissions to create leases for the leader elections
orCannot perform leader election. All agents will behave as leader.
- Check if the agent has the correct permissions to create leases.
NAME APIGROUP↑ GET LIST WATCH CREATE PATCH UPDATE DELETE DEL-LISTleases coordination.k8s.io ✓ ✓ ✓ ✓ × ✓ × ×
- Check if you can reach the platform from the agent:
kubectl exec -it -n steadybit-agent steadybit-agent-0 -- curl -k https://steadybit-platform.steadybit-platform.svc.cluster.local:8080
- Check if the agent can reach the Websocket port of the platform.
- This is usally port 7878 and can be configured in the platform manifest via environment variable
STEADYBIT_WEB_PUBLIC_EXPERIMENT_PORT
- Please also check your ingress configuration.
spec:rules:- http:paths:- pathType: Prefixpath: /wsbackend:service:name: steadybit-platformport:number: 7878- pathType: Prefixpath: /backend:service:name: steadybit-platformport:number: 80
Last modified 10mo ago