fix(ROX-33305): add StackRox image pull secret to qa-image-scanning-test namespace#19182
fix(ROX-33305): add StackRox image pull secret to qa-image-scanning-test namespace#19182tommartensen wants to merge 1 commit intomasterfrom
Conversation
…est namespace Image metadata from registry tests run in qa-image-scanning-test. The default service account in that namespace was never given image pull secrets; only per-deployment secrets (e.g. quay-image-scanning-test) were created for specific iterations. Call addStackroxImagePullSecret in ImageScanningTest.setupSpec() after ensuring the namespace exists so the default SA has quay and public-dockerhub secrets and can pull StackRox/Quay images when deployments do not set their own. Partially generated by AI.
|
/test help |
|
Skipping CI for Draft Pull Request. |
|
/test gke-latest-qa-e2e-tests |
|
Images are ready for the commit at 9546b0b. To use with deploy scripts, first |
|
/test gke-latest-qa-e2e-tests |
|
@tommartensen: 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. |
Image metadata from registry tests run in qa-image-scanning-test. The default service account in that namespace was never given image pull secrets; only per-deployment secrets (e.g. quay-image-scanning-test) were created for specific iterations. Call addStackroxImagePullSecret in ImageScanningTest.setupSpec() after ensuring the namespace exists so the default SA has quay and public-dockerhub secrets and can pull StackRox/Quay images when deployments do not set their own.
Partially generated by AI.
Description
change me!
User-facing documentation
Testing and quality
Automated testing
How I validated my change
change me!