The StackRox Kubernetes Security Platform version 3.0.42 includes new features, bug fixes, and system changes. To upgrade to this release from a previous version, see the Upgrade StackRox section.
You can now use Comments and Tags to specify what’s happening with violations and processes to keep your team up to date. Comments and tags are available in various views, for example, you can add comments and tags for,
Violations in the following views:
Processes in the following views:
- ROX-4671: We addressed an issue that caused high CPU usage in Sensor.
- ROX-4607: Previously, the admission controller didn’t enforce policies with single cluster scope. We’ve fixed this issue.
- ROX-4580: Previously, in the Configuration Management view, the StackRox portal didn’t show background for selected deployments listed in the Service Account details panel. Now the StackRox portal now shows the details.
- ROX-4543 and ROX-4272: Previously, in the Configuration Management view, the StackRox portal didn’t show deployments details panel when you selected from Image > Deployment. The StackRox portal now correctly shows the details.
- ROX-4429: Previously, the automatic upgrades wouldn’t work if the cluster reported some resources as unavailable. We’ve updated the StackRox Kubernetes Security Platform to ensure that automatic upgrades work as usual as long as the required resources are available on the cluster.
You can now snooze CVEs for a specified time such as a day, a week, two weeks, a month, or indefinitely (until you unsnooze).
- You can now request pretty-printed JSON responses for all v1 API endpoints by
?prettypath parameter in your requests. For more information, see the Use the API topic.
- You can use:
- We’ve added a new Deployment Name field in the Deployment Details panel for the Violations and Risk views.
- In the Risk view, the browser address bar now shows the complete address (including the applied filtering) when you use local page filtering. You can copy and share the address for the filtered view with others.
We’ve updated the Security Context Constraint (SCC) priority to
0 so that they
don’t supersede default SCCs.
|Update||Enable PKI authentication||Added information about configuring custom endpoints by using a YAML configuration file.|
|Update||Resource requirements||Added information about recommended machine type and cores for deploying Central and updated the architecture diagram.|
|Update||Integrate with image registries||Included the registry integration explanation.|
|Update||Examine images||Added information about differences in the CVSS scores between Red Hat Security Advisory (RHSA) CVSS score and the CVSS score visible in the StackRox portal.|
|Update||Get started||Updated the StackRox Kubernetes Security Platform architecture diagram.|
|Update||Integrate with CI systems||Added instructions for running the |
|Added||Evaluate the StackRox Kubernetes Security Platform||Added instructions for evaluating Deploy-time policies, Run-time policies, and Risks report.|
We're happy to help! Reach out to us to discuss questions, issues, or feature requests.