SKIP UPGRADE Sonarqube bump to 9.2.6-bb.17-1
Skipping upgrade since too much has change in master CI for release-1.16.x branch
Package Owner Merge Request
For release-1.16.x branch, this will be included in Patch Release 1.16.2 of BigBang
Package Changes
Fixing duplicate definitions of nodeSelector, tolerations & affinity.
https://repo1.dso.mil/platform-one/big-bang/apps/developer-tools/sonarqube/-/merge_requests/46/diffs
https://repo1.dso.mil/platform-one/big-bang/apps/developer-tools/sonarqube/-/tags/9.2.6-bb.17-1
Merge request reports
Activity
added sonarqube label
added statusreview label
mentioned in commit d6e09c31
mentioned in issue #634 (closed)
@micah.nagel Do you have a specification for setting containerd runtime memory limit for sonarqube?
Edited by Gabriel Borcean
This might help? https://repo1.dso.mil/platform-one/big-bang/bigbang/-/blob/master/docs/guides/prerequisites/minimum_hardware_requirements.md
@michaelmcleroy put together a spreadsheet with data for our expected/recommended CPU/Memory limits for most pods. If that doesn't help we'd recommend just tweaking as needed for your environment. It definitely varies from customer to customer depending on how much memory someone has available + how much load their system is getting. The defaults are in general a "best effort" for a small production deployment.
mentioned in merge request micah.nagel/micahnagel!122 (closed)
mentioned in merge request micah.nagel/micahnagel!123 (closed)
mentioned in merge request micah.nagel/micahnagel!124 (closed)
mentioned in merge request micah.nagel/micahnagel!125 (closed)
mentioned in merge request micah.nagel/micahnagel!126 (closed)
mentioned in merge request micah.nagel/micahnagel!127 (closed)
