Supported Environments and Prerequisites for Kubernetes Compliance

Overview

This article provides the supported environments for a Kubernetes Compliance integration and the prerequisites required for the integration.

The supported Kubernetes provider environments are listed below:

The supported versions of Kubernetes are listed below:

The supported versions of Helm are listed below:

The supported versions of Terraform are listed below:

A Linux Agent access token is required prior to completing the integration steps for any Kubernetes environment.

If you only want to monitor compliance configuration, it is recommended that you create a new access token. You can then disable or enable the Agent token for this integration without affecting other integrations that use this token.
If you want to monitor both compliance configuration and workload security, you may want to use an existing access token. For example, if you have an Agent token in use for workload security on Kubernetes clusters, it may be better to combine this integration with the same access token.

note

You only need to generate the access token as the Agent is installed during the integration steps.

Ensure that an AWS Configuration integration exists for your AWS account or organization.
Ensure that the AWS CLI is installed and configured to access your EKS environment.

Ensure that a Google Cloud Configuration integration exists for your Google Cloud project or organization.
Ensure that the Google Cloud CLI (gcloud) is installed and configured to access your GKE environment.

Choose one of the following options to integrate Lacework with your Kubernetes cluster: