You can upgrade or downgrade the Kubernetes Sensor remotely through the Carbon Black Cloud console.

This method:
  • Does not require direct admin access to the cluster because the operator handles the upgrade or downgrade.
  • Automatically enables or disables supported features depending on the sensor version that you select.
  • Does not override customized values with default values.
  • Does not change the cluster or sensor configuration.
  • Requires an Operator version 6.1.0 or higher.

Procedure

  1. On the left navigation pane of the console, do one of the following depending on your system configuration and role:
    • If you are assigned Kubernetes Security DevOps role and your system has only Containers Security feature, Click Inventory > Clusters.
    • If you are assigned any other role and your system has Container security and other Carbon Black Cloud features, click Inventory > Kubernetes > Clusters.
  2. Locate the cluster to update.
  3. In the Options dropdown menu, click Edit.
  4. Optionally add any new labels for the cluster. Click Next.
  5. Select the Sensor version from the dropdown list. This should usually be the latest version, which is the first version listed.
    Selected Kubernetes sensor version
  6. Included features for the selected sensor version are displayed. Click Next.
  7. Select the check box for Apply changes directly to the cluster.
    Remotely upgrade or downgrade a Kubernetes Sensor
    Note:
    • When using the option to Apply changes directly to the cluster, you do not need to copy and run commands in a terminal window.
    • If you manage the cluster using Helm or other infrastructure-as-code, that system will override the settings you establish using this procedure.
  8. Click Done.

Results

It takes between two and three minutes for the new sensor to become effective. If the upgraded sensor version supports new functionality, such as CNDR, that new functionality is automatically enabled by the Operator. This capability assumes that you are running the latest version of the Operator.

If you are downgrading the sensor version and the downgraded sensor does not support a particular functionality, the Operator disables that functionality upon the downgrade action.

Any remote upgrade or downgrade of the Kubernetes Sensor is noted in the Audit Log.

What to do next

Check the Kubernetes Sensor Status and Health