| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
This release contains a minor addition (suspend field) to the Custom Resource Definitions (CRDs), Helm does not update CRDs after the initial installation. If you are planning on using the suspend field make sure that your CRDs are up to date.
To upgrade the CRDs you can run the following script or grab the latest CRDs from the git repo at the v5.6.0 tag:
kubectl apply -f https://raw.githubusercontent.com/secureCodeBox/secureCodeBox/v5.6.0/operator/crds/execution.securecodebox.io_scans.yaml
kubectl apply -f https://raw.githubusercontent.com/secureCodeBox/secureCodeBox/v5.6.0/operator/crds/execution.securecodebox.io_scheduledscans.yamlFull Changelog: v5.5.0...v5.6.0
Full Changelog: v5.4.0...v5.5.0
Full Changelog: v5.3.0...v5.4.0
Full Changelog: v5.2.0...v5.3.0
Full Changelog: v5.1.0...v5.2.0
This release brings some long awaited improvements and optimizations.
Some of this required breaking changes, these are listed below.
To avoid naming collisions with other cluster‑scoped resources, the operator's ClusterRole formerly called manager-role has been renamed to securecodebox‑manager-role, and the corresponding ClusterRoleBinding manager-rolebinding is now securecodebox‑manager-rolebinding. The official Helm chart will automatically create and reference these new names when you update the operator.
If you maintain a custom deployment that directly references manager-role or manager-rolebinding, be sure to update those references to securecodebox‑manager-role and securecodebox‑manager-rolebinding respectively.
The kubeauditScope on the trivy ScanType chart was renamed to k8sScanScope Scope. The previous name was used for consistency with the kubeaudit ScanType, but it never really made sense and was confusing.
The default k8sScanScope scope was also changed from cluster to namespace, The cluster mode needs cluster wide permissions, which makes the trivy chart hard to install in properly locked down RBAC setups.
The integrated Elasticsearch and Kibana Helm charts have been dropped from the Persistence ElasticSearch Hook. These charts were intended as a quick-start option, but since Elastic no longer provides their own Helm charts, they have been removed. The documentation has been updated with guidance on setting up an Elasticsearch cluster using the ECK operator.
The default Elasticsearch index has been updated from scbv2 to scb. The inclusion of v2 was a confusing oversight that has been outdated since the release of secureCodeBox v3.
If you had previously ingested finding using the scbv2 index prefix you can keep using it by setting the indexPrefix helm value back to scbv2 or by migrating your existing indexes to match the new naming scheme.
Due to upcoming deprecations in Bitnami Helm charts, the operator's MinIO integration has been changed from using the Bitnami MinIO subchart to a direct MinIO deployment using the official docker.io/minio/minio image.
⚠️ Important Migration Notes:
For Production Environments:
The included MinIO deployment is intended only for quickstart and development setups. For production environments, you should:
If you need to continue using the embedded MinIO for development, the new deployment will create a fresh MinIO instance with the same default bucket configuration.
Third Release Candidate of the secureCodeBox v5 release. ☺️
This now also includes an alternative minio stack to prepare for the upcoming bitnami depracations.
For a preview of the upcoming changes, see the upgrading notes and/or the v5 milestone
| Back | FazBrowse Home | New Git URL |