Integrate Trivy Operator with Licensight¶

Prerequisites¶

Webhook URL from data source
A personal access token

Configure Trivy Operator¶

There are two Trivy Operator variables that you need to configure:

Variable	Description	Value
`OPERATOR_WEBHOOK_BROADCAST_URL`	The webhook endpoint to send the reports to	The webhook URL of data source provided by Licensight
`OPERATOR_WEBHOOK_BROADCAST_CUSTOM_HEADERS`	Comma separated `key:value` to send webhook notifications with custom headers. Default is ``	X-API-Key:<access-token>

Example:

...
OPERATOR_WEBHOOK_BROADCAST_URL: https://my-tenant.licensight.com/data/resources/datasources/xxxxxxxxxxxxxxxx/webhook
OPERATOR_WEBHOOK_BROADCAST_CUSTOM_HEADERS: X-API-Key:xxxxxxxxxxxxxxxx
...

If you deploy Trivy Operator using official Helm chart, there are two ways to configure it

Add directly to the Helm values (not secure)¶

operator:
  webhookBroadcastURL: https://my-tenant.licensight.com/data/resources/datasources/xxxxxxxxxxxxxxxx/webhook
  webhookBroadcastCustomHeaders: X-API-Key:xxxxxxxxxxxxxxxx
  ...

Put values in a Secret (recommended)¶

Put these values in a Secret:

OPERATOR_WEBHOOK_BROADCAST_URL: https://my-tenant.licensight.com/data/resources/datasources/xxxxxxxxxxxxxxxx/webhook
OPERATOR_WEBHOOK_BROADCAST_CUSTOM_HEADERS: X-API-Key:xxxxxxxxxxxxxxxx

In Helm values, configure Trivy Operator to use values from Secret:

operator:
  valuesFromSecret: <name-of-secret>

The values from Secret will override Helm AND ConfigMap values

Note: You may need to restart Trivy Operator for the configuration changes to take effect

For more information, see the Trivy Operator documentation.