Skip to content
Default test

feat: Add possibility to configure securityContext for each pod #415

Sign in to view logs

feat: Add possibility to configure securityContext for each pod

feat: Add possibility to configure securityContext for each pod #415

Triggered via pull request January 11, 2024 20:46
@ppawlowskippawlowski
opened #275
feat-podsecuritycontext
Status Success
Total duration 17s
Artifacts –

test.yml

on: pull_request
build
10s
build
Fit to window
Zoom out
Zoom in

Annotations

70 warnings
build
The following actions uses node12 which is deprecated and will be forced to run on node16: azure/setup-helm@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
[MEDIUM] CVE-2023-48795 (openssh-client-common-9.3_p2-r0) failed: openssh-client-common-9.3_p2-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-48795 (openssh-client-default-9.3_p2-r0) failed: openssh-client-default-9.3_p2-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-48795 (openssh-keygen-9.3_p2-r0) failed: openssh-keygen-9.3_p2-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-26159 (follow-redirects-1.15.3) failed: follow-redirects-1.15.3#L0
trivy-junit-results.xml
[MEDIUM] GHSA-v78c-4p63-2j6c (moment-timezone-0.5.34) failed: moment-timezone-0.5.34#L0
trivy-junit-results.xml
All 2 runs failed: [MEDIUM] CVE-2022-25883 (semver-7.3.7): semver-7.3.7#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-26136 (tough-cookie-4.0.0) failed: tough-cookie-4.0.0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-0842 (xml2js-0.4.23) failed: xml2js-0.4.23#L0
trivy-junit-results.xml
[HIGH] CVE-2022-4450 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0215 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0286 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0464 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-2097 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-4304 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-0465 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2022-4450 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0215 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0286 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0464 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-2097 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-4304 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-0465 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[CRITICAL] CVE-2022-37434 (zlib-1.2.12-r0) failed: zlib-1.2.12-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-45857 (axios-0.27.0) failed: axios-0.27.0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-26159 (follow-redirects-1.15.3) failed: follow-redirects-1.15.3#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-33987 (got-11.8.3) failed: got-11.8.3#L0
trivy-junit-results.xml
[HIGH] CVE-2022-25881 (http-cache-semantics-4.1.0) failed: http-cache-semantics-4.1.0#L0
trivy-junit-results.xml
[MEDIUM] GHSA-v78c-4p63-2j6c (moment-timezone-0.5.34) failed: moment-timezone-0.5.34#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-25896 (passport-0.5.2) failed: passport-0.5.2#L0
trivy-junit-results.xml
[HIGH] CVE-2022-24999 (qs-6.9.6) failed: qs-6.9.6#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-25883 (semver-7.3.5) failed: semver-7.3.5#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-25883 (semver-7.3.7) failed: semver-7.3.7#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-26136 (tough-cookie-4.0.0) failed: tough-cookie-4.0.0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-0842 (xml2js-0.4.23) failed: xml2js-0.4.23#L0
trivy-junit-results.xml
[HIGH] CVE-2022-4450 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0215 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0286 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0464 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-2097 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-4304 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-0465 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2022-4450 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0215 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0286 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0464 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-2097 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-4304 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-0465 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[CRITICAL] CVE-2022-37434 (zlib-1.2.12-r0) failed: zlib-1.2.12-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-45857 (axios-0.27.0) failed: axios-0.27.0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-26159 (follow-redirects-1.15.3) failed: follow-redirects-1.15.3#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-33987 (got-11.8.3) failed: got-11.8.3#L0
trivy-junit-results.xml
[HIGH] CVE-2022-25881 (http-cache-semantics-4.1.0) failed: http-cache-semantics-4.1.0#L0
trivy-junit-results.xml
[MEDIUM] GHSA-v78c-4p63-2j6c (moment-timezone-0.5.34) failed: moment-timezone-0.5.34#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-25896 (passport-0.5.2) failed: passport-0.5.2#L0
trivy-junit-results.xml
[HIGH] CVE-2022-24999 (qs-6.9.6) failed: qs-6.9.6#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-25883 (semver-7.3.5) failed: semver-7.3.5#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-25883 (semver-7.3.7) failed: semver-7.3.7#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-26136 (tough-cookie-4.0.0) failed: tough-cookie-4.0.0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-0842 (xml2js-0.4.23) failed: xml2js-0.4.23#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-48795 (openssh-client-common-9.3_p2-r0) failed: openssh-client-common-9.3_p2-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-48795 (openssh-client-default-9.3_p2-r0) failed: openssh-client-default-9.3_p2-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-48795 (openssh-keygen-9.3_p2-r0) failed: openssh-keygen-9.3_p2-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-26159 (follow-redirects-1.15.3) failed: follow-redirects-1.15.3#L0
trivy-junit-results.xml
[MEDIUM] GHSA-v78c-4p63-2j6c (moment-timezone-0.5.34) failed: moment-timezone-0.5.34#L0
trivy-junit-results.xml
All 2 runs failed: [MEDIUM] CVE-2022-25883 (semver-7.3.7): semver-7.3.7#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-26136 (tough-cookie-4.0.0) failed: tough-cookie-4.0.0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-0842 (xml2js-0.4.23) failed: xml2js-0.4.23#L0
trivy-junit-results.xml