add network policy option for gitlab
Summary
- Add network policy toggle for gitlab
- update release tag for gitlab package
Various changes to Gitlab Package:
- network polices
- limit default user permissions
- add helm tests for CI pipelines
- remove unneeded registry.host key in values.yaml
- documentation about backing up the gitlab-rails secret
- ironbank image for praefect
Closes #438
Closes #456 (closed)
Merge request reports
Activity
changed milestone to %1.9.0
added Big Bang Security gitlab kindfeature priority4 statusdoing labels
added statusreview label and removed statusdoing label
added statusdoing label and removed statusreview label
added statusreview label and removed statusdoing label
mentioned in issue #456 (closed)
requested review from @runyontr
requested review from @joshwolf
Resolved by kevin.wilderSee https://repo1.dso.mil/platform-one/big-bang/bigbang/-/blob/master/chart/templates/mattermost/operator/values.yaml#L9 for the proper way to pass in NP values. Let me know if that makes sense.
Edited by Micah Nagel- Last reply by bhearn
mentioned in issue #393 (closed)
added 3 commits
-
0915ae3c...40934683 - 2 commits from branch
master - cd0b806d - Merge branch 'master' of https://repo1.dso.mil/platform-one/big-bang/bigbang into 438-gitlab-update
-
0915ae3c...40934683 - 2 commits from branch
- Resolved by kevin.wilder
Reviewing the package MR now, I think I have a couple concerns:
- monitoring policy should be conditional on monitoring being enabled, and specify a port(s) for metrics so that ingress is only allowed to metrics specific ports
- allowing all egress by default is NOT ideal. If there's a good justification that's fine, but what is the purpose of this? External DB/Redis (if so should be conditional on those)?
- Last reply by kevin.wilder
mentioned in commit 33686505
mentioned in issue #469 (closed)
mentioned in issue #634 (closed)