For each Kubernetes cluster you want Soveren to monitor, you'll require a Soveren Agent.
You can create, modify, and delete Agents via the agents page in the Soveren app.
Each Agent is characterized by its
If you have multiple clusters, and thus multiple Agents, Soveren will display them separately on the data map. The Agent's name will define the name of the cluster on the data map.
You can also automate the naming of your clusters in Soveren by setting the names of the clusters in your configuration files.
token allows the Soveren app to identify the Agent during communication.
We recommend adding the
token to your own configuration file, such as
values.yaml, to simplify operational procedures.
Use unique Agents and tokens for different clusters
If you're managing multiple clusters, please create unique Agents for each one, with distinct tokens. Using the same token for different clusters will result in them appearing as a single deployment perimeter on the data map, making it challenging to discern which flow belongs to which cluster.
Verifying image signatures
Ensure the authenticity and integrity of downloaded images by validating their digital signatures.
We use Cosign for image signing. Below is the public key you should employ when verifying the signatures:
-----BEGIN PUBLIC KEY----- MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEF5frUnmoziugp0E1uOZJNTzQHJx3 zf93Qcg/kJO1RpV/2SkVK+u0NH+M1K4ja6nr0pIjIyFwP3L6rpKY9p0Kcg== -----END PUBLIC KEY-----
We utilize Helm for deployment. The installation procedure is as follows:
kubectl create namespace soverenio helm repo add soveren https://soverenio.github.io/helm-charts helm install -n soverenio soveren-agent soveren/soveren-agent --set digger.token="<TOKEN>"
We recommend that instead of adding
<TOKEN> to the command line, you incorporate the
token into your own configuration file, such as
values.yaml. Then, use the following commands instead of the ones above:
kubectl create namespace soverenio helm repo add soveren https://soverenio.github.io/helm-charts helm install -n soverenio soveren-agent soveren/soveren-agent -f path_to/values.yaml
Updating the Agent to the latest version is straightforward:
helm repo update soveren helm upgrade soveren-agent soveren/soveren-agent -n soverenio -f path_to/values.yaml
You can check the latest version information in the current chart.
Scaling down or removing Agents
To completely uninstall the Agent, use the following command:
helm -n soverenio uninstall soveren-agent
If you wish to address performance issues with any individual component, you can temporarily scale it down using the following command:
kubectl -n soverenio scale deployment.apps/<DEPLOYMENT_NAME> --replicas=0
<DEPLOYMENT_NAME> can be one of the following:
To scale it back up, use:
kubectl -n soverenio scale deployment.apps/<DEPLOYMENT_NAME> --replicas=1
Scaling down interceptors does not offer any practical benefits. It is more effective to completely remove the Agent and then bring it back up using the standard update or deploy command.