Helm Chart Deployment via GitOps Tools

If you are managing your Kubernetes clusters using a GitOps framework, you can easily deploy and manage the Tenable One Cloud Exposure Helm chart using industry-standard tools instead of running manual helm install commands.

By establishing your Git repository as the single source of truth, GitOps tools automatically synchronize your cluster with your desired configuration, prevent manual configuration drift, and make tracking your Helm chart's versioning and parameters trivial through your Git version control history.

Tenable supports both Flux and Argo CD for managing your Helm chart deployments.

Flux Setup

Flux utilizes a modular configuration style based on custom Kubernetes resources (HelmRepository, HelmRelease, and Kustomization) to pull updates directly from your Git repository.

Initialize Flux

Before deploying the Helm chart, ensure Flux is installed and properly configured for your cluster environment. You can follow the official implementation steps from the Flux Get Started Guide.

Configure the Repository Layout

To deploy the Cloud Exposure Helm chart, organize your files in your Git repository using the following directory layout:

Copy
./clusters/my-cluster/
  tenable-sync.yaml        # Flux Kustomization (The entry point)
./apps/tenable/
  kustomization.yaml       # Grouping all the files together
  tenable-repo.yaml        # HelmRepository source definition
  tenable-release.yaml     # HelmRelease deployment configuration
  tenable-secrets.yaml     # Kubernetes Secret for sensitive tokens

Add the Configuration Manifests

In your Git repository, add the following YAML files inside your application directory (./apps/tenable/).

Tenable-Repo.Yaml

This manifest defines where Flux should fetch the official Cloud Exposure Helm charts.

Copy

YAML

apiVersion: source.toolkit.fluxcd.io/v1
kind: HelmRepository
metadata:
  name: tenable
  namespace: tenable-cloud-security-kubernetes-cluster
spec:
  interval: 1h
  url: https://charts.tenable.com/

Tenable-Release.Yaml

This contains the deployment instructions. It links the Cloud Exposure chart version, maps your custom public values, and binds the private authentication values from your secrets file to the Helm chart.

Copy

YAML

apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: tenable-cloud-security-kubernetes-cluster
  namespace: tenable-cloud-security-kubernetes-cluster
spec:
  interval: 1h
  install:
    createNamespace: true
  chart:
    spec:
      chart: cloud-security-kubernetes-cluster
      version: '>=1.0.0'
      sourceRef:
        kind: HelmRepository
        name: tenable
        namespace: flux-system
  values:
    apiUrl: "{}"
    containerImage:
      registryUsername: "{}"
  valuesFrom:
    - kind: Secret
      name: tenable-cloud-security-secrets
      valuesKey: apiKeyToken
      targetPath: apiKeyToken
    - kind: Secret
      name: tenable-cloud-security-secrets
      valuesKey: registryPassword
      targetPath: containerImage.registryPassword

Tenable-Secrets.Yaml

This manifest holds the sensitive token and authentication data for your Helm chart. Ensure these values are Base64 encoded before applying them.

Copy

YAML

apiVersion: v1
kind: Secret
metadata:
  name: tenable-cloud-security-secrets
  namespace: tenable-cloud-security-kubernetes-cluster
type: Opaque
data:
  apiKeyToken: {}
  registryPassword: {}

Kustomization.Yaml

This file must reside in the same ./apps/tenable/ directory to bundle your Kubernetes manifests together.

Copy

YAML

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
  - tenable-repo.yaml
  - tenable-secrets.yaml
  - tenable-release.yaml

Create the Entrypoint

Create an entrypoint manifest in your cluster configuration path (./clusters/my-cluster/tenable-sync.yaml). This tells Flux which folder to monitor and synchronize to run the Helm chart.

Copy

YAML

apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
  name: tenable-app
  namespace: flux-system
spec:
  interval: 10m
  path: ./apps/tenable
  prune: true
  sourceRef:
    kind: GitRepository
    name: flux-system

Argo CD Setup

Argo CD handles Helm chart management directly through a unified Application Custom Resource Definition (CRD) and provides a centralized web dashboard to track your Helm chart's deployment health.

Install Argo CD

To install Argo CD into your cluster, you can use the official Helm repository commands:

Copy

Bash

# Add the official Argo Helm repository
helm repo add argo https://argoproj.github.io/argo-helm

# Install Argo CD into its own namespace
helm install argo-cd argo/argo-cd --namespace argocd --create-namespace

# Make sure all platform pods are running successfully
kubectl get pods -n argocd

Useful Argo CD Actions

You can track, watch, and maintain your Cloud Exposure Helm chart state from the command line using actions outlined below.

Argo CD Application Manifest

To deploy the Helm chart, you must create a configuration file in YAML format known as an Application manifest. This manifest instructs Argo CD to monitor the Tenable Helm repository and deploy its components based on your specific cluster parameters.

You should save and commit this YAML configuration file directly into your tracked Git repository.

Save the following configuration as Application.yaml:

Copy

YAML

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: tenable-cloud-security
  namespace: argocd
spec:
  project: default
  source:
    repoURL: https://charts.tenable.com
    chart: cloud-security-kubernetes-cluster
    targetRevision: "1.1.0" # The CHART VERSION you need to run (fetch via: helm search repo tenable)
    helm:
      parameters:
        - name: apiKeyToken
          value: ""
        - name: apiUrl
          value: ""
        - name: containerImage.registryUsername
          value: ""
        - name: containerImage.registryPassword
          value: ""
        - name: name
          value: "cluster"
        - name: containerImage.registry
          value: ""
  destination:
    server: https://kubernetes.default.svc
    namespace:       # The target deployment namespace for the Tenable sensor
  syncPolicy:
    automated:
      selfHeal: true # Automatically reverts manual cluster modifications back to the Git state
      prune: true    # Automatically removes resources deleted from your config

Apply the Application Manifest

Run the following command to register the application manifest and initialize the application tracking inside Argo CD:

Copy

Bash

kubectl apply -f Application.yaml
Note: The Helm chart deployment lifecycle is actively managed and rendered internally by Argo CD. As a result, you will not see the deployment listed if you run local terminal commands like helm list -A.

Watch the Application Status

Run this command to check the high-level operational status (such as Running, Pending, or Degraded) of your managed applications:

Copy

Bash

kubectl get applications -n argocd

View Helm Chart Orchestration Details

Run this command to view live synchronization events, target revision status, and in-depth logging configurations for the Helm chart:

Copy

Bash

kubectl describe application tenable-cloud-security -n argocd

Delete the Application

Run this command to remove the application configuration and pull the running Helm chart resources out of your target cluster:

Copy

Bash

kubectl delete application tenable-cloud-security -n argocd