SKIP UPGRADE: Move gatekeeper overrides to BigBang
Package Owner Merge Request
No package changes.
Additional Details
- Adds Istio enable as a condition for checking istio constraints
- Moves
registry.dso.mil
into BB override - Formatting
Related to #672 (closed)
Merge request reports
Activity
changed milestone to %1.16.0
added Big Bang Security ~2865 gatekeeper kindfeature statusdoing labels
changed milestone to %1.15.0
added statusreview label and removed statusdoing label
- Automatically resolved by Michael McLeroy
Related to and potentially closes https://repo1.dso.mil/platform-one/big-bang/bigbang/-/issues/604 ?
- Resolved by Michael McLeroy
Might require a new issue, but sounds like it should be covered under this MR Title, what if we made a value at
gatekeeper.violations
orgatekeeper.exceptions
that then does a dig to insert them into the bigbang values template rather than in an override values file that could overlap with what BigBang already sets?Eg:
- Values file
gatekeeper: exceptions: allowedHostFilesystem: - namespace1
- chart/templates/gatekeeper/values.yaml
allowedHostFilesystem: match: excludedNamespaces: # required for monitoring's prometheus-node-exporter to get node metrics excludedNamespaces: # Prometheus-node-exporter needs access to host to get node metrics {{- if .Values.monitoring.enabled }} - monitoring {{- end }} # Maybe a range or if/with function, just an example {{ dig "gatekeeper" "exceptions" $values }}
added 31 commits
-
562b1684...43069d0e - 30 commits from branch
master
- 60bc11d1 - Merge branch 'master' into 672-move-gatekeeper-overrides
-
562b1684...43069d0e - 30 commits from branch
added 1 commit
- d6438ae8 - chore(gatekeeper): remove dead code for istio
added 5 commits
-
d6438ae8...85162caa - 4 commits from branch
master
- 74b3418e - Merge branch 'master' into 672-move-gatekeeper-overrides
-
d6438ae8...85162caa - 4 commits from branch
enabled an automatic merge when the pipeline for 74b3418e succeeds
mentioned in issue #692 (closed)
mentioned in commit 79105876
mentioned in issue #632 (closed)
mentioned in issue #633 (closed)