FAQ: Kubernetes
This article contains a list of frequently asked questions related to Kubernetes within Tenable One Cloud Exposure.
Cluster Connector Requirement for On-Premises or Self-Managed Clusters
The connector functions as an API token that's required for Cloud Exposure to connect to your cluster. You can add one connector for all relevant clusters in your environment.
Kubernetes Cluster Connector API Key Permissions in Tenable
The Kubernetes Cluster Connector in Tenable is an API key used to authenticate and enable secure communication between a Kubernetes cluster and the Cloud Exposure platform. Its primary role is to facilitate the integration of Kubernetes environments with Tenable for monitoring and analysis purposes.
Despite the name, the Kubernetes Cluster Connector API key has a narrow and specific scope. It is strictly limited to Kubernetes-related operations and does not grant access to broader Tenable APIs, such as querying entity data or performing account-level actions. Attempts to use it outside of its intended purpose, such as accessing other parts of the platform, will be rejected.
Cluster Account Association
When the helm chart is installed on a cluster, Cloud Exposure detects the cluster account location as follows:
- If the associated cloud account was already connected, the cluster is added to the relevant account scope (folder) for the cloud provider.
- If the associated cloud account hasn't been connected, Tenable attempts to identify the location based on the account of the worker node.
-
If no such account is detected, Tenable adds the cluster to the On-Premises default account.
Note: Although in most situations, clusters added to this default account are indeed on-premises, other cluster types may also be mapped to this folder. For example, clusters belonging to cloud providers that aren't supported by Cloud Exposure. - You can override the detected account location by adding the following to the Helm command: --set accountId={accountId}. See Add Your Cluster for details.
Resource Visibility in Console
Resources will appear the next time data is synchronized in your environment.
Scanning New Container Images
The sensor scans nodes for new or updated container images within approximately 30 minutes. Findings are updated the next time Tenable syncs data in your environment.
OpenShift Cluster Support
Yes. You can connect them via Helm Chart.
Moving Clusters
Uninstall the cluster via Helm Chart, and then reinstall it. To uninstall, run the following command on the cluster: helm uninstall tenable-kubernetes-cluster-connector -n tenable
Custom Cluster Names
Yes. When you connect a self-managed/on-prem cluster, the default name is the DNS name. You can override this by adding the following to the Helm command: --set name={name}. See Connect a Cluster via Helm Chart for more information.
Agent Version
You can get the version by running kubectl on the cluster and looking at the workload pod logs: kubectl logs <tenable connector pod name> -n <namespace> | grep Version
For connector pods, search for Version in the output. The version will be represented by BuildVersion and buildVersion in the output for admission controller pods and sensor pods, respectively.
Admission Controller
The webhook listens on port 8443 by default because it is a secure HTTPS port commonly used for Kubernetes admission webhooks. It ensures that all incoming control requests from worker nodes are processed securely.
In a private GKE setup, network restrictions such as firewall rules, VPC configurations, or other security mechanisms might block worker nodes from reaching the webhook on port 8443. This can prevent the Admission Controller from functioning properly.
To allow worker nodes to access the webhook:
- Firewall Rules: Ensure that firewall rules permit traffic from all worker nodes to the webhook endpoint on port 8443.
- VPC Peering: If the webhook runs in a different VPC, set up proper peering and routing.
- Network Policies: In Kubernetes, check and modify any NetworkPolicy that may be blocking communication.
- Endpoint Accessibility: Verify that the webhook service is correctly exposed and reachable within the cluster.
Yes, if necessary, the webhook can be configured to listen on a different port. However, this requires updating the webhook configuration in Kubernetes and ensuring firewall rules allow traffic to the new port.
The customer overwrite option allows users to specify a custom configuration if the default port (8443) is not accessible. This could involve defining a different port or setting up alternative networking rules to ensure connectivity.
To enable the Vulnerable Container Images policy, the admission controller identifies the container images being deployed by reading your image pull secrets. Tenable grants permission to list secrets, but the admission controller inspects only image pull secrets. This access is disabled by default. Enable it with --set admissionController.readSecrets=true. This requires Tenable Kubernetes Helm chart version 1.1.6 or later.
Deploying Cloud Exposure Helm Chart from a Private Repository
To deploy the Cloud Exposure Helm chart from a private Git repository follow these steps:
-
Clone the Helm chart from the official Tenable repo by running:
helm repo add <local path/cloned repo>, or configure your 3rd party continues deployment platform to point to the copy.Note: If necessary, copy the repo/chart to the location from which you wish to install the chart. - Update your helm install command to point to your private repo or local path, rather than Tenable’s public GitHub repository.
Yes. Tenable recommends syncing the private repo with the latest Helm chart releases at least once every two weeks. This ensures access to the latest features, improvements, and security updates.
If the deployment requires the use of private container registries, customers must also mirror Tenable's container images to their private registries. This includes updating image references in the Helm values as needed.
For more information see the documentation.
Like the Helm chart, the images must also be updated regularly, as the images contain the actual runtime components that receive frequent updates for features, performance, and security.
How to Use a Specific Sensor Version for Kubernetes Clusters
You can only download the latest sensor version that Tenable publishes. However, you can manage and pin specific versions yourself by using Clusters with a Private Registry.
Once you download the latest version, push it to your private registry and tag it according to your versioning needs. From there, you control which tag your cluster pulls.