ROX-19064: Scanner V4 DB CI - PVC Storage Class#19833
ROX-19064: Scanner V4 DB CI - PVC Storage Class#19833
Conversation
|
Skipping CI for Draft Pull Request. |
|
/test all |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #19833 +/- ##
=======================================
Coverage 49.60% 49.60%
=======================================
Files 2763 2763
Lines 208339 208339
=======================================
Hits 103341 103341
Misses 97331 97331
Partials 7667 7667
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
🚀 Build Images ReadyImages are ready for commit a5062f0. To use with deploy scripts: export MAIN_IMAGE_TAG=4.11.x-562-ga5062f0d70 |
|
/test gke-qa-e2e-tests |
|
/test all |
|
@dcaravel: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Description
Using an SSD backed PVC for Scanner V4 DB will help it be ready quickly in CI.
This PR enables the PVC's Storage Class name to be configured per job and sets that name for various jobs known to benefit from it. This is necessary because jobs deploy to different cluster flavors which use different storage class names.
The storage class name is set appropriately regardless which of the 3 supported install mechanisms are used (manifest, helm, or operator)
Not every job requires this setting, for example the OCP targets use "ssd-csi" is the default storage class. Leaving the name unset will result in the cluster's default storage class being used.
In the future when/if all cluster flavors are updated to use a SSD storage class by default the explicit settings can be removed. For now this change favored a path of least resistance that is easy to reason about.
User-facing documentation
Testing and quality
Automated testing
The changes themselves are tests
How I validated my change
Against StackRox Scanner these changes will be tested by CI as part of this PR
Against Scanner V4 these changes were validated in #19236 and will be validated again in a future PR when Scanner V4 is officially turned on in CI.