Edit on GitHub

21.04 Update 1 Release Notes

1. Overview

The following table outlines the release particulars:

Build

21.04.421

Code name

Hamilton, 21.04 update 1

Release date

27 May 2021

Type

Maintenance release

SHA-256 digest

b09f51f524e431e767197fd276aeafa3ba63491aad0b11e52ef4e8451e6c675a

2. Improvements, fixes, and performance enhancements

  • Adds support for Kubernetes resource labels discovery in CRI-O runtime.

  • Adds support for Podman 3.

  • Fixes an issue with applying custom rules to WAAS policy.

  • Exposes the proxy read timeout configuration for WAAS.

  • Fixes an issue with twistcli IaC Scan for a large number of resources (<1000).

  • Changes default effect from “Disable” to “Allow” for user defined Bots in WAAS policy.

  • Fixes an issue with Intelligence Stream update for tenant projects that are hosted on machines with low resources.

  • Fixes an issue with OAuth in OpenShift 4.6.

  • Fixes an issue with UI response time for page load on Defend > Images > Registry Settings.

  • Fixes an issue with filesystem monitoring on pods that use NFS volumes with root squashing enabled. With this fix, NFS volumes with root squashing enabled are skipped to avoid errors.

  • Fixes an issue with the missing content-encoding header when WAAS is enabled.

  • Adds support for package license information in the twistcli image, host, and code repository scans output file.

3. Known issues

  • Defender containers in Defender DaemonSets still display as vulnerable after upgrade. This happens because the auto-upgrade mechanism updates the Defender binary only, not the entire image, and the vulnerabilities exist in the image base layer. To resolve the issue, redeploy all Defender DaemonSets.

4. Upcoming deprecations

Starting on June 14, 2021, we’ll publish API documentation for our stable endpoints only.

Stable endpoints have always been fully supported, and we have been committed to minimizing changes to them so that your integrations don’t break when upgrading to newer versions of Compute.

Starting with our next release (codenamed Iverson), we’ll further enhance how we support our API with versioned endpoints. All stable endpoints will be versioned. Versioned endpoints will be supported for the current release and the previous two releases (that is, Console will serve all three versions). When you upgrade Compute, integrations can still access the endpoints from previous releases, so you can expect integrations to remain fully functional after upgrades, with full support across three major release cycles.