Release notes: 3.0.38

Find out what's new in version 3.0.38.

1 minute read

The StackRox Kubernetes Security Platform version 3.0.38 includes bug fixes and system changes. In this version, we’re also laying the groundwork for exciting new features in forthcoming releases. To upgrade to this release from a previous version, see the Upgrade StackRox section.

Important bug fixes

Resolved in version 3.0.38.0

  • Bug ROX-3772: Previously, if you selected Retry Upgrade or Upgrade Available for automatic upgrades in a multi-cluster environment, the upgrade would trigger on different clusters rather than the selected one. We’ve fixed this issue.
  • Bug ROX-3922: We’ve improved the email integration for compatibility with Office365 and other systems that use the STARTTLS LOGIN authentication method.
  • Bug ROX-3932: We’ve fixed an issue in the StackRox portal, where sorting the clusters based on the sensor version didn’t work as expected.

Resolved in version 3.0.38.1

  • Bug ROX-4009: In version 3.0.38.0 only, sending a violation to Jira can cause Central to crash. We’ve resolved this issue in version 3.0.38.1.

Resolved in version 3.0.38.2

  • Bug ROX-4078: We’ve fixed an issue where a large number of unnecessary duplicate processes remained.

    Along with resolving this, we’ve also:

    • reduced memory consumption in Sensor related to network flows, and
    • improved the performance of risk calculation for deployments.

Resolved in version 3.0.38.3

  • Bug ROX-4209: We’ve fixed an issue where the compliance scan would not correctly consider UID 0 as root for the CSI Docker 4.1 benchmark.

Important system changes

API

We’ve added the /v1/group endpoint. You can use it to retrieve a single group by exact property match.

Questions?

We're happy to help! Reach out to us to discuss questions, issues, or feature requests.

© 2021 StackRox Inc. All rights reserved.