Extension Discovery

Overview
Extensions needs to be discovered by the agent. There are two ways to do that:
Kubernetes Auto Discovery
The agent is looking for services and pods with an annotation steadybit.com/extension-auto-discovery. These annotations are already added to our extensions if you use our official helm charts. You can find an example in our extension-datadog​
Kuberenetes Auto Discovery fine tuning
If you want to fine tune the auto discovery, you can fine tune the mechanism to:
include only extensions pods matching a given label selector
exclude extensions pods matching a given label selector
using Helm Chart
using Environment Variables
outpost:
  extensions:
    autodiscovery:
      matchLabelsInclude:
        custom/extension-i-want-to-discover: true
      matchLabelsExclude:
        app.kubernetes.io/name: extension-host
STEADYBIT_AGENT_EXTENSIONS_AUTODISCOVERY_MATCHLABELS_0_KEY=custom/extension-i-want-to-discover STEADYBIT_AGENT_EXTENSIONS_AUTODISCOVERY_MATCHLABELS_0_VALUE=true STEADYBIT_AGENT_EXTENSIONS_AUTODISCOVERY_MATCHLABELSEXCLUDE_0_KEY=app.kubernetes.io/name STEADYBIT_AGENT_EXTENSIONS_AUTODISCOVERY_MATCHLABELSEXCLUDE_0_VALUE=extension-host
Manual Extension Registration
If you can't use the Kubernetes Auto Discovery, you need to register the extension manually. You can do that by adding environment variables to the agent. See the respective documentation of the extension or the extension kits' respective documentation.
​ActionKit​
​DiscoveryKit​
​EventKit​

Install on Amazon ECS

Using Mutual TLS for Extensions

Last modified 1mo ago