fix enterprise mode deployments (containerSecurityContext and bitnami common)
General MR
Looks like we forgot to apply this containerSecurityContext to the anchore-feeds-db postgres dependency when we upgrade postgresql. This is the root cause of #109 (closed).
When testing, I found out that enterprise mode was broken in main in general per #111 (closed). This was due to a conflict between redis's new version of the bitnami common lib, and postgres's old version of the bitnami common lib. I went ahead and bumped bitnami, and things are working now. In addition to testing in a test cluster, I also made sure to compare all of the outputted yamls from helm template with enterprise turned on.
Note that CI is intermittently failing. This has been occurring since the last renovate was completed, and was not caused by this MR. I opened #112 (closed) so that someone can take a look at it.
Merge request reports
Activity
changed milestone to %2.14.0
added anchore community-contribution kindbug priority3 statusreview labels
assigned to @jrb
added statusblocked label and removed statusreview label
This is currently blocked because the main branch is broken.
Edited by Jonathan Braswellmentioned in issue #109 (closed)
- Resolved by Mario Lunato
Blocked by: #111 (closed)
- Last reply by Jonathan Braswell
added 1 commit
- 67529ed5 - bump common chart dep to fix conflict when enterprise is enabled
added 1 commit
- aef14905 - bump common chart dep to fix conflict when enterprise is enabled
added statusreview label and removed statusblocked label
requested review from @nicole.dupree, @montgomery.marcus, @mlunato47, and @brettcharrier
mentioned in commit 74432ea1
mentioned in merge request big-bang/bigbang!3391 (merged)