By default, the agent assumes that your cluster uses the Docker container runtime. If this is not the case, you need to setagent.containerRuntime
to eithercontainerd
orcrio
.
helm_release
resource will be used. Analogous to the above procedure, the agent key needs to be specified. See the following provider and resource definition for Terraform:Kubernetes
as a DaemonSet
you need to define the DaemonSet
YAML file. Below you will see an example of a YAML file to run the steadybit agent.steadybit-agent
in which the DaemonSet
will be created. It allows you to tag and isolate the agents or even stop all of them at once by simply deleting the steadybit-agent
namespace.replace-with-agent-key
with your specific Agent-Key and run the shown commands to encode the key correctly.echo -n _:<replace-with-agent-key> | base64
and fill in the result into the value for the auth
keyecho -n '{"auths":{"docker.steadybit.io":{"auths":"<replace-with-encoded-key-from-step-1>"}}}' | base64
.dockerconfigjson
keykubectl
:Service Account
and RBAC Authorization
for the steadybit-agent
. With the access to the K8s API, the agent can provide further information to the platform for identifying potential targets. More information about Service Accounts or RBAC Authorization is available in the Kubernetes docs.