Skip to content

Commit 9769cb8

Browse files
committed
docs(cascading-scan): Added Upgrading note to set cascadingrules.enabled to true explicitly
Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
1 parent 426c9f3 commit 9769cb8

1 file changed

Lines changed: 11 additions & 1 deletion

File tree

‎UPGRADING.md‎

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -140,4 +140,14 @@ These images are usually used for testing and demo purposes. If you use these im
140140
Previously scheduled scans generated by the container autodiscovery are named in the format `scan-image_name-at-image_hash`. The resulting scan pod will be called `scan-scan-image_name-at-image_hash`.
141141
To avoid the duplicate “scan-scan”, the scheduled scans from the container autodiscovery are renamed. As a result, the container autodiscovery will no longer correctly “recognize” the old scans anymore. It will instead create new scans according to the new naming scheme. The old scheduled scans must be deleted manually.
142142

143-
➡️ [Reference: #1193](https://github.com/secureCodeBox/secureCodeBox/pull/1193)
143+
➡️ [Reference: #1193](https://github.com/secureCodeBox/secureCodeBox/pull/1193)
144+
145+
146+
### Cascading rules are disabled by default
147+
Having the Cascading rules enabled by default on scanner helm install, has led to some confusion on the users side as mentioned in issue [#914](https://github.com/secureCodeBox/secureCodeBox/issues/914). As a result Cascading rules will have to be explicitly enabled by setting the `cascadingRules.enabled` value to `true`. For example as so:
148+
```yaml
149+
helm upgrade --install nmap secureCodeBox/nmap --set=cascadingRules.enabled=true
150+
```
151+
152+
➡️ [Reference: #1347](https://github.com/secureCodeBox/secureCodeBox/pull/1347)
153+

0 commit comments

Comments
 (0)