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

This method:
  • Requires direct admin access to the cluster.
  • Generates a new cluster configuration (custom resource).
  • Automatically enables or disables supported features depending on the sensor version that you select.
  • Overwrites customized values with default values when the custom resource is applied.

Procedure

  1. Open a terminal window.
  2. 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.
  3. Locate the cluster to update.
  4. In the Options dropdown menu, click Edit.
  5. Optionally add any new labels for the cluster. Click Next.
  6. 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
  7. Included features for the selected sensor version are displayed. Click Next.
  8. Copy the commands from the Finish Edits page and run them in the terminal window.
    Example of code to copy into the terminal window
    Important: Do not select Apply changes directly to the cluster for this method of upgrade or downgrade. That option is relevant only if you are not directly accessing the cluster, which is covered in Upgrade or Downgrade the Kubernetes Sensor Remotely through the Console.
  9. 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.

What to do next

Check the Kubernetes Sensor Status and Health