Deploying in Sensor-Only mode

The following guide will walk you through the steps of deploying in Sensor-Only mode, as the final step to setup inCloud Managed. If you're not in the process setting up inCloud Managed, you should follow this guide to deploy groundcover.

Kubernetes

Deploying groundcover sensors in a Kubernetes cluster is done by deploying the groundcover Helm chart with specific overrides. There are multiple ways to deploy the Helm chart which are listed below.

After setting up inCloud Managed you will receive configuration values from the groundcover team that are needed for the next steps.

If you haven't received those values please contact the groundcover team before proceeding.

Creating an overrides file

In order to deploy in sensor-only mode, you will need to provide installation values similar to these:

global:
  backend:
    enabled: false
  ingress:
    site: {inCloud_Site}

{inCloud_Site} is your unique backend identifier, which is needed for the sensors to send data to your backend. This value will be sent to you by the grouncover team after inCloud Managed is set up.

Example

In this example the {inCloud_Site} received by the groundcover team will be example.platform.grcv.io.

The following values will be needed in the deployment:

global:
  backend:
    enabled: false
  ingress:
    site: example.platform.grcv.io

Deploying the sensors

Choose any of the installation methods below to deploy the groundcover helm chart.

Don't forget to add the overrides the from previous step to the deployment values!

1. Using the groundcover CLI

2. Using Helm

3. Using ArgoCD