Comment on page
Install on Kubernetes
You must be able to access the following URLs via HTTPS (443) on your target environment:
- https://platform.steadybit.com (Platform)
- https://steadybit.github.io (Kubernetes helm repository)
- https://ghcr.io and https://github.com (Container Images)
Just run the script while connected to your Kubernetes cluster.
helm repo add steadybit https://steadybit.github.io/helm-charts
helm repo update
helm install steadybit-outpost --namespace steadybit-outpost \
--set outpost.key=<replace-with-agent-key> \
--set global.clusterName=<replace-with-cluster-name> \
To configure the installation, specify the values on the command line using the
--setflag, or provide a YAML file with your values using the
Keep an eye on OOMing / crash looping agents and extensions after installation. The memory usage highly depends on the number of discovered targets. We try to provide reasonable defaults, but you might need to adapt the resource limits to your use case.
For example, to increase the memory limits for the outpost:
By default, the agent assumes that your cluster uses the
containerdruntime. If this is not the case, you need to add
In case of a managed Kubernetes service, there might be a vendor-specific method to check the container runtime. In case you have access on the
kubectl, you can get the container runtime via
kubectl get nodes -o wide
If you are running on-prem, make sure to set the URL of the platform:
By default, the helm chart installs the extensions
extension-kubernetes. Further extensions can be enabled via helm values of steadybit-outpost. For example,
extension-postmancan be enabled by setting
extension-postman.enabled=true. See our GitHub Repository for a detailed list of all the configuration parameters.
Alternatively, you can also install extensions independently with their own helm charts. The installation instructions are listed in the Github repositories of the extension and can be browsed via the Reliability Hub.