Release notes: 3.0.36

Find out what's new in version 3.0.36.

1 minute read

The StackRox Kubernetes Security Platform version 3.0.36 includes new features, 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.

New features

Upload license from StackRox portal

In addition to uploading your StackRox Kubernetes Security Platform license by using the roxctl command-line interface, you can now upload your license by using the StackRox Portal as well. You can use it to upload your license when you are installing the StackRox Kubernetes Security Platform or updating your license after its expiry. See the License activation section for more details.

Important bug fixes

Resolved in version 3.0.36.0

  • Bug ROX-3777: We’ve fixed an issue with the Sensor upgrader not working with custom CA certificates. The sensor upgrader now mounts custom certificates during the upgrade.
  • Bug ROX-3767: Previously, exporting compliance scan results in CSV format by using the API, sometimes returned older unsupported CIS Docker 1.1.0 and CIS Kubernetes 1.4.1 results. We’ve resolved this issue.
  • Bug ROX-3561: Removed experimental compliance management schedule APIs that were unintentionally exposed.

Resolved in version 3.0.36.1

  • Bug ROX-3802: We’ve fixed an issue that prevented opening the Compliance and the Configuration Management views in Firefox and Safari browsers.

Important system changes

General

We made updates to various YAML files (deployments, daemonsets and pod security policies) and removed references to the deprecated extensions/v1beta1 Kubernetes API’s. This makes the StackRox Kubernetes Security Platform compatible with Kubernetes 1.16, however, it won’t affect existing StackRox Kubernetes Security Platform deployments. For more information, see the Kubernetes blog Deprecated APIs Removed In 1.16: Here’s What You Need To Know.

API

We removed the following experimental API’s:

  1. /v1/complianceManagement/schedules GET
  2. /v1/complianceManagement/schedules POST
  3. /v1/complianceManagement/schedules/{schedule_id} POST
  4. /v1/complianceManagement/schedules/{schedule_id} DELETE

Questions?

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

© 2021 StackRox Inc. All rights reserved.