OpsLevel Agent
The OpsLevel agent is a multi-facet application that runs in your cloud and connects with OpsLevel to support multiple functionalities for OpsLevel. The current functionalities are:
- Kubernetes Service Detection (Aliases)
https://github.com/OpsLevel/opslevel-agent
Primer
To see the agent in action you can watch this primer video
https://opslevel.zoom.us/clips/share/A2F3MRZiQkhwOTJDRVJ0ZUYtMnNtMnJUMzBRAQ
Prerequisites
- Make sure you have the OpsLevel Helm chart repository added.
- Make sure you have the "kubernetes integration" installed in your opslevel account
Values.yaml
The bare minimum values file look like this
secret:
data:
OPSLEVEL_API_TOKEN: "XXXXX"helm install opslevel-agent opslevel/opslevel-agent -f values.yamlMultiple Clusters
If you intend to deploy the agent to multiple clusters you may want to create a unique
integration tile in your OpsLevel account for each cluster so that you know which cluster the recommendations are coming from.
If you do this you'll need to specify the integration's alias in the values file you'll want the agent to submit for like this:

agent:
integration: "Prod Cluster"Resource Targeting
By default the agent will target the following resources:
- v1/Service
- apps/v1/Deployment
- apps/v1/StatefulSet
- apps/v1/DaemonSet
- batch/v1/CronJob
but if you want other resource types to make suggestions you can add configuration so long as the
resource types show up when you use kubectl api-resources --verbs="get,list".
The following restricts the agent to only syncronize Service and APIService resources:
configmap:
data:
config.yaml: |
selectors:
- apiVersion: "v1"
kind: Service
- apiVersion: "apiregistration.k8s.io/v1"
kind: APIServiceUpdated 14 days ago

