Resolved Issues in 5.10.2
Issue | Description |
|---|---|
E-138765 | Operator install preventing C-VEN activation for On-Prem C-VEN scripts could not complete after Kubernetes Operator installation, preventing C-VEN activations for some on-prem environments. This issue was resolved by accounting for C-VEN script execution time within the agent manager. |
E-140093 | C-VEN policy update accumulation inflating storage C-VEN per-workload SQLite databases (fwtest.db) accumulated unused pages from policy updates, inflating the database size on disk. This issue was resolved by implementing an automatic mechanism to vacuum this storage. |
E-141801 | Pod to external host communication bypassing enforcement C-VEN couldn't retry connections when the CRI socket became faulty or unavailable, causing policy application to skip some pods. This issue was resolved by implementing a retry mechanism. |