The StackRox Kubernetes Security Platform version 2.4.20 includes several new features and enhancements. To upgrade to this release from a previous version, see the Upgrade StackRox section.
The StackRox Kubernetes Security Platform enforces licensing restrictions in version 2.4.20 and higher.
Contact your sales representative or StackRox support if you don’t have a license.
An enhanced network graph providing easier scaling and better interactivity is now available. You can now move namespaces and see more details to understand how your applications communicate.
You can now backup your database to an Amazon S3 bucket and restore from a saved copy. To get started, open Platform Configuration > Integrations and set up an S3 backup schedule.
When you’re evaluating your infrastructure for compliance, now it’s easier to see the details of related entities for every cluster, node, namespace, deployment, or control. With the updated layout, you now can stay on one page and use multiple tabs to navigate and view all related entity information.
You can now write policies to find services that are exposed using
NodePort services, or with
hostPort pod configurations.
- ROX-1892: In the previous version, removing nodes from cluster didn’t delete related objects from memory, resulting in the Sensor consuming large amounts of memory. The Sensor service now correctly frees memory when you remove nodes from a secured cluster.
- ROX-1955: Previously, there was a mismatch between the actual default timeout
and the default timeout displayed in the
roxctlcommand-line interface (CLI)
roxctlCLI now correctly sets default timeouts for different commands, especially for database backups. You can still specify timeouts explicitly.
- ROX-2011: In versions 220.127.116.11 through 18.104.22.168, some users couldn’t get past an “Authenticating” message when accessing the StackRox portal. Version 22.214.171.124 resolves this issue.
- ROX-1959: If you have created custom Role-Based Access Control (RBAC)
roles, you must grant users
Readaccess to the
Licensesresource before they can access the StackRox portal.
We're happy to help! Reach out to us to discuss questions, issues, or feature requests.