Comment on page

Install on Kubernetes

This method will install the Steadybit outpost agent on your Kubernetes Cluster using Helm. So you need to have helm installed.
Prerequisites
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)
Installation
To deploy the outpost agent to Kubernetes, you can copy the installation script from the setup page in the SaaS platform.
Alternatively, you can update the script below with the name of your Kubernetes cluster and your agent key, which you find in the platform's setup page.
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 \
  --create-namespace \
  --set outpost.key=<replace-with-agent-key> \
  --set global.clusterName=<replace-with-cluster-name> \
  steadybit/steadybit-outpost
To configure the installation, specify the values on the command line using the --set flag, or provide a YAML file with your values using the -f flag.
For more configuration options have a look at our steadybit/helm-charts repository.
Resource limits
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:
  --set outpost.resources.limits.memory=1Gi
Configure Container Runtime for Docker or CRI-O
By default, the agent assumes that your cluster uses the containerd runtime. If this is not the case, you need to add--set extension-container.container.runtime=docker or cri-o.
Determine Container Runtime on a Node
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
The column CONTAINER-RUNTIME shows you the runtime you are using. You can find further in the official Kubernetes documentation.
Configure custom Platform for On-Prem
If you are running on-prem, make sure to set the URL of the platform: --set outpost.registerUrl=<your-platform-url>
Additional Extensions
By default, the helm chart installs the extensions extension-container, extension-host, extension-http and extension-kubernetes. Further extensions can be enabled via helm values of steadybit-outpost. For example, extension-postman can be enabled by settingextension-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.

Architecture

Install on Linux Hosts

Last modified 11d ago