add anchore network policy toggle

Summary

also bump the version

changed milestone to %1.9.0

added Big Bang Security keycloak kindfeature priority4 statusdoing labels

marked this merge request as draft

changed the description

added 1 commit

• 71d9bbb6 - update anchore network policy toggle

Compare with previous version

added 1 commit

• 2f9c93a2 - bump synker anchore tags

Compare with previous version

marked this merge request as ready

changed the description

added anchore label

removed keycloak label

added 13 commits

• 2f9c93a2...f86e5860 - 12 commits from branch master
• 1f6b85a8 - Merge branch 'master' of https://repo1.dso.mil/platform-one/big-bang/bigbang...

Compare with previous version

added 5 commits

• 1f6b85a8...4c676723 - 4 commits from branch master
• 62d921d7 - Merge branch 'master' into 443-anchore-update

Compare with previous version

Seeing some weird behavior with the engine upgrade job running on an install from master -> this branch. Trying to debug and see what's going on....

I'm going to notify our Helm release engineer about this, but I'm not sure if there's anything we can do about the intermittent failures in the near-term

added statusreview label and removed statusdoing label

requested review from @micah.nagel and @ryan.j.garcia

added 47 commits

• 62d921d7...74219a0b - 46 commits from branch master
• 9e5911e4 - Merge branch 'master' of https://repo1.dso.mil/platform-one/big-bang/bigbang...

Compare with previous version

@micah.nagel @ryan.j.garcia I tried upgrading 10+ times (master:1.12.13-bb.0 -> 443-anchore-update:1.12.15-bb.0), but I can't seem to replicate the behavior we were seeing before

resolved all threads

approved this merge request