Skip to content

03-Helm chart release #110

03-Helm chart release

03-Helm chart release #110

Re-run triggered October 1, 2024 14:12
Status Success
Total duration 20m 40s
Artifacts

03-helm-release.yaml

on: workflow_dispatch
Matrix: e2e-test / e2e-test
helm-chart-release
8s
helm-chart-release
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 42 warnings
relevancy_large_image: results_xml_format/relevancy_large_image.xml#L1
'RelevancyEnabledLargeImage' object has no attribute 'get_filtered_SBOM_from_storage'
relevancy_java_and_python: results_xml_format/relevancy_java_and_python.xml#L1
the files in the CVEs in the storage is not as expected, expected: ['CVE-2018-20225', 'CVE-2007-4559'] storage: ['CVE-2007-4559']
relevancy_java: results_xml_format/relevancy_java.xml#L1
the files in the CVEs in the storage is not as expected, expected: ['CVE-2016-2781', 'CVE-2023-21968', 'CVE-2017-7658', 'CVE-2017-7657', 'CVE-2022-2048', 'CVE-2020-27216', 'CVE-2017-9735', 'CVE-2017-7656', 'CVE-2009-5045', 'CVE-2023-26049', 'CVE-2023-26048', 'CVE-2021-28169', 'CVE-2009-5046', 'CVE-2022-2047', 'CVE-2021-34428', 'CVE-2016-20013', 'CVE-2016-20013', 'CVE-2017-11164', 'CVE-2016-20013'] storage: ['CVE-2016-2781', 'CVE-2023-21968', 'CVE-2016-20013']
relevancy_extra_large_image: results_xml_format/relevancy_extra_large_image.xml#L1
'RelevancyEnabledExtraLargeImage' object has no attribute 'get_filtered_SBOM_from_storage'
relevantCVEs: results_xml_format/relevantCVEs.xml#L1
the files in the CVEs in the storage is not as expected, expected: ['CVE-2016-2781', 'CVE-2022-1664', 'CVE-2023-28642', 'CVE-2023-27561', 'CVE-2022-29162', 'CVE-2023-25809', 'CVE-2021-43784', 'CVE-2022-29526', 'CVE-2021-3999', 'CVE-2022-23219', 'CVE-2022-23218', 'CVE-2021-35942', 'CVE-2021-3326', 'CVE-2021-27645', 'CVE-2020-6096', 'CVE-2020-29562', 'CVE-2020-27618', 'CVE-2019-25013', 'CVE-2016-20013', 'CVE-2016-10228', 'CVE-2021-3999', 'CVE-2022-23219', 'CVE-2022-23218', 'CVE-2021-35942', 'CVE-2021-3326', 'CVE-2021-27645', 'CVE-2020-6096', 'CVE-2020-29562', 'CVE-2020-27618', 'CVE-2019-25013', 'CVE-2016-20013', 'CVE-2016-10228', 'CVE-2021-43618', 'CVE-2022-1271', 'CVE-2023-29491', 'CVE-2022-29458', 'CVE-2021-39537', 'CVE-2022-28321', 'CVE-2022-28321', 'CVE-2022-1587', 'CVE-2022-1586', 'CVE-2019-20838', 'CVE-2020-14155', 'CVE-2017-11164', 'CVE-2023-31484', 'CVE-2020-16156', 'CVE-2021-36087', 'CVE-2021-36086', 'CVE-2021-36085', 'CVE-2021-36084', 'CVE-2023-0286', 'CVE-2022-0778', 'CVE-2023-0215', 'CVE-2022-4450', 'CVE-2022-4304', 'CVE-2022-2097', 'CVE-2022-2068', 'CVE-2022-1292', 'CVE-2023-0465', 'CVE-2023-0464', 'CVE-2023-0466', 'CVE-2022-4415', 'CVE-2022-3821', 'CVE-2021-3997', 'CVE-2023-26604', 'CVE-2023-29491', 'CVE-2022-29458', 'CVE-2021-39537', 'CVE-2023-0286', 'CVE-2022-0778', 'CVE-2023-0215', 'CVE-2022-4450', 'CVE-2022-4304', 'CVE-2022-2097', 'CVE-2022-2068', 'CVE-2022-1292', 'CVE-2023-0465', 'CVE-2023-0464', 'CVE-2023-0466', 'CVE-2023-29383', 'CVE-2013-4235', 'CVE-2023-31484', 'CVE-2020-16156', 'CVE-2023-31484', 'CVE-2020-16156', 'CVE-2023-31484', 'CVE-2020-16156', 'CVE-2022-37434', 'CVE-2022-29154', 'CVE-2018-25032', 'CVE-2023-24540', 'CVE-2023-24538', 'CVE-2022-23806', 'CVE-2021-38297', 'CVE-2023-29400', 'CVE-2023-24539', 'CVE-2023-24537', 'CVE-2023-24536', 'CVE-2023-24534', 'CVE-2022-41725', 'CVE-2022-41724', 'CVE-2022-41723', 'CVE-2022-41715', 'CVE-2022-32189', 'CVE-2022-30635', 'CVE-2022-30633', 'CVE-2022-30632', 'CVE-2022-30631', 'CVE-2022-30630', 'CVE-2022-30580', 'CVE-2022-2880', 'CVE-2022-2879', 'CVE-2022-28327', 'CVE-2022-28131', 'CVE-2022-27664', 'CVE-2022-24921', 'CVE-2022-24675', 'CVE-2022-23773', 'CVE-2022-23772', 'CVE-2021-44716', 'CVE-2021-41772', 'CVE-2021-41771', 'CVE-2021-39293', 'CVE-2021-29923', 'CVE-2023-24532', 'CVE-2022-41717', 'CVE-2022-32148', 'CVE-2022-29526', 'CVE-2022-1962', 'CVE-2022-1705', 'CVE-2021-44717', 'CVE-2020-29511', 'CVE-2020-29509', 'CVE-2022-30629', 'CVE-2022-37434', 'CVE-2018-25032'] storage: ['CVE-2016-2781', 'CVE-2022-1664', 'CVE-2023-28642', 'CVE-2023-27561', 'CVE-2022-29162', 'CVE-2023-25809', 'CVE-2021-43784', 'CVE-2022-29526', 'CVE-2021-3999', 'CVE-2022-23219', 'CVE-2022-23218', 'CVE-2021-35942', 'CVE-2021-3326', 'CVE-2021-27645', 'CVE-2020-6096', 'CVE-2020-29562', 'CVE-2020-27618', 'CVE-2019-25013', 'CVE-2016-20013', 'CVE-2016-10228', 'CVE-2021-43618', 'CVE-2022-1271', 'CVE-2022-28321', 'CVE-2022-28321', 'CVE-2022-1587', 'CVE-2022-1586', 'CVE-2019-20838', 'CVE-2020-14155', 'CVE-2017-11164', 'CVE-2023-31484', 'CVE-2020-16156', 'CVE-2021-36087', 'CVE-2021-36086', 'CVE-2021-36085', 'CVE-2021-36084', 'CVE-2023-0286', 'CVE-2022-0778', 'CVE-2023-0215', 'CVE-2022-4450', 'CVE-2022-4304', 'CVE-2022-2097', 'CVE-2022-2068', 'CVE-2022-1292', 'CVE-2023-0465', 'CVE-2023-0464', 'CVE-2023-0466', 'CVE-2022-4415', 'CVE-2022-3821', 'CVE-2021-3997', 'CVE-2023-26604', 'CVE-2023-29491', 'CVE-2022-29458', 'CVE-2021-39537', 'CVE-2023-29383', 'CVE-2013-4235', 'CVE-2023-31484', 'CVE-2020-16156', 'CVE-2023-31484', 'CVE-2020-16156', 'CVE-2023-31484', 'CVE-2020-16156', 'CVE-2022-37434', 'CVE-2022-29154', 'CVE-2018-25032', 'CVE-2023-24540', 'CVE-2023-24538', 'CVE-2022-23806', 'CVE-2021-38297', 'CVE-2023-29400', 'CVE-2023-24539', 'CVE-2023-24537', 'CVE-2023-24536', 'CVE-2023-24534', 'CVE-2022-41725', 'CVE-2022-41724', 'CVE-2022-41723', 'CVE-2022-41715', 'CVE-2022-32189', 'CVE-2022-30635', 'CVE-2022-30633', 'CVE-2022-30632', 'CVE-2022-30631', 'CVE-2022-30630', 'CVE-2022-30580', 'CVE-2022-2880', 'CVE-2022-2879', 'CVE-2022-28327', 'CVE-2022-28131', 'CVE-2022-27664', 'CVE-2022-24921', 'CVE-2022-24675', 'CVE-2022-23773', 'CVE-2022-23772', 'CVE-2021-44716', 'CVE-2021-41772', 'CVE-2021-41771', 'CVE-2021-39293', 'CVE-2021-29923', 'CVE-2023-24532', 'CVE-2022-41717', 'CVE-2022-32148', 'CVE-2022-29526', 'CVE-2022-1962', 'CVE-2022-1705', 'CVE-2021-44717', 'CVE-2020-29511', 'CVE-2020-29509', 'CVE-2022-30629', 'CVE-2022-37434', 'CVE-2018-25032']
relevancy_java_and_python: results_xml_format/relevancy_java_and_python.xml#L1
the files in the CVEs in the storage is not as expected, expected: ['CVE-2018-20225', 'CVE-2007-4559'] storage: ['CVE-2007-4559']
relevantCVEs: results_xml_format/relevantCVEs.xml#L1
the files in the CVEs in the storage is not as expected, expected: ['CVE-2016-2781', 'CVE-2022-1664', 'CVE-2023-28642', 'CVE-2023-27561', 'CVE-2022-29162', 'CVE-2023-25809', 'CVE-2021-43784', 'CVE-2022-29526', 'CVE-2021-3999', 'CVE-2022-23219', 'CVE-2022-23218', 'CVE-2021-35942', 'CVE-2021-3326', 'CVE-2021-27645', 'CVE-2020-6096', 'CVE-2020-29562', 'CVE-2020-27618', 'CVE-2019-25013', 'CVE-2016-20013', 'CVE-2016-10228', 'CVE-2021-3999', 'CVE-2022-23219', 'CVE-2022-23218', 'CVE-2021-35942', 'CVE-2021-3326', 'CVE-2021-27645', 'CVE-2020-6096', 'CVE-2020-29562', 'CVE-2020-27618', 'CVE-2019-25013', 'CVE-2016-20013', 'CVE-2016-10228', 'CVE-2021-43618', 'CVE-2022-1271', 'CVE-2023-29491', 'CVE-2022-29458', 'CVE-2021-39537', 'CVE-2022-28321', 'CVE-2022-28321', 'CVE-2022-1587', 'CVE-2022-1586', 'CVE-2019-20838', 'CVE-2020-14155', 'CVE-2017-11164', 'CVE-2023-31484', 'CVE-2020-16156', 'CVE-2021-36087', 'CVE-2021-36086', 'CVE-2021-36085', 'CVE-2021-36084', 'CVE-2023-0286', 'CVE-2022-0778', 'CVE-2023-0215', 'CVE-2022-4450', 'CVE-2022-4304', 'CVE-2022-2097', 'CVE-2022-2068', 'CVE-2022-1292', 'CVE-2023-0465', 'CVE-2023-0464', 'CVE-2023-0466', 'CVE-2022-4415', 'CVE-2022-3821', 'CVE-2021-3997', 'CVE-2023-26604', 'CVE-2023-29491', 'CVE-2022-29458', 'CVE-2021-39537', 'CVE-2023-0286', 'CVE-2022-0778', 'CVE-2023-0215', 'CVE-2022-4450', 'CVE-2022-4304', 'CVE-2022-2097', 'CVE-2022-2068', 'CVE-2022-1292', 'CVE-2023-0465', 'CVE-2023-0464', 'CVE-2023-0466', 'CVE-2023-29383', 'CVE-2013-4235', 'CVE-2023-31484', 'CVE-2020-16156', 'CVE-2023-31484', 'CVE-2020-16156', 'CVE-2023-31484', 'CVE-2020-16156', 'CVE-2022-37434', 'CVE-2022-29154', 'CVE-2018-25032', 'CVE-2023-24540', 'CVE-2023-24538', 'CVE-2022-23806', 'CVE-2021-38297', 'CVE-2023-29400', 'CVE-2023-24539', 'CVE-2023-24537', 'CVE-2023-24536', 'CVE-2023-24534', 'CVE-2022-41725', 'CVE-2022-41724', 'CVE-2022-41723', 'CVE-2022-41715', 'CVE-2022-32189', 'CVE-2022-30635', 'CVE-2022-30633', 'CVE-2022-30632', 'CVE-2022-30631', 'CVE-2022-30630', 'CVE-2022-30580', 'CVE-2022-2880', 'CVE-2022-2879', 'CVE-2022-28327', 'CVE-2022-28131', 'CVE-2022-27664', 'CVE-2022-24921', 'CVE-2022-24675', 'CVE-2022-23773', 'CVE-2022-23772', 'CVE-2021-44716', 'CVE-2021-41772', 'CVE-2021-41771', 'CVE-2021-39293', 'CVE-2021-29923', 'CVE-2023-24532', 'CVE-2022-41717', 'CVE-2022-32148', 'CVE-2022-29526', 'CVE-2022-1962', 'CVE-2022-1705', 'CVE-2021-44717', 'CVE-2020-29511', 'CVE-2020-29509', 'CVE-2022-30629', 'CVE-2022-37434', 'CVE-2018-25032'] storage: ['CVE-2016-2781', 'CVE-2022-1664', 'CVE-2023-28642', 'CVE-2023-27561', 'CVE-2022-29162', 'CVE-2023-25809', 'CVE-2021-43784', 'CVE-2022-29526', 'CVE-2021-3999', 'CVE-2022-23219', 'CVE-2022-23218', 'CVE-2021-35942', 'CVE-2021-3326', 'CVE-2021-27645', 'CVE-2020-6096', 'CVE-2020-29562', 'CVE-2020-27618', 'CVE-2019-25013', 'CVE-2016-20013', 'CVE-2016-10228', 'CVE-2021-43618', 'CVE-2022-1271', 'CVE-2022-28321', 'CVE-2022-28321', 'CVE-2022-1587', 'CVE-2022-1586', 'CVE-2019-20838', 'CVE-2020-14155', 'CVE-2017-11164', 'CVE-2023-31484', 'CVE-2020-16156', 'CVE-2021-36087', 'CVE-2021-36086', 'CVE-2021-36085', 'CVE-2021-36084', 'CVE-2023-0286', 'CVE-2022-0778', 'CVE-2023-0215', 'CVE-2022-4450', 'CVE-2022-4304', 'CVE-2022-2097', 'CVE-2022-2068', 'CVE-2022-1292', 'CVE-2023-0465', 'CVE-2023-0464', 'CVE-2023-0466', 'CVE-2022-4415', 'CVE-2022-3821', 'CVE-2021-3997', 'CVE-2023-26604', 'CVE-2023-29491', 'CVE-2022-29458', 'CVE-2021-39537', 'CVE-2023-29383', 'CVE-2013-4235', 'CVE-2023-31484', 'CVE-2020-16156', 'CVE-2023-31484', 'CVE-2020-16156', 'CVE-2023-31484', 'CVE-2020-16156', 'CVE-2022-37434', 'CVE-2022-29154', 'CVE-2018-25032', 'CVE-2023-24540', 'CVE-2023-24538', 'CVE-2022-23806', 'CVE-2021-38297', 'CVE-2023-29400', 'CVE-2023-24539', 'CVE-2023-24537', 'CVE-2023-24536', 'CVE-2023-24534', 'CVE-2022-41725', 'CVE-2022-41724', 'CVE-2022-41723', 'CVE-2022-41715', 'CVE-2022-32189', 'CVE-2022-30635', 'CVE-2022-30633', 'CVE-2022-30632', 'CVE-2022-30631', 'CVE-2022-30630', 'CVE-2022-30580', 'CVE-2022-2880', 'CVE-2022-2879', 'CVE-2022-28327', 'CVE-2022-28131', 'CVE-2022-27664', 'CVE-2022-24921', 'CVE-2022-24675', 'CVE-2022-23773', 'CVE-2022-23772', 'CVE-2021-44716', 'CVE-2021-41772', 'CVE-2021-41771', 'CVE-2021-39293', 'CVE-2021-29923', 'CVE-2023-24532', 'CVE-2022-41717', 'CVE-2022-32148', 'CVE-2022-29526', 'CVE-2022-1962', 'CVE-2022-1705', 'CVE-2021-44717', 'CVE-2020-29511', 'CVE-2020-29509', 'CVE-2022-30629', 'CVE-2022-37434', 'CVE-2018-25032']
relevantCVEs: results_xml_format/relevantCVEs.xml#L1
the files in the CVEs in the storage is not as expected, expected: ['CVE-2022-28391', 'CVE-2021-33587', 'CVE-2022-23540', 'CVE-2022-23539', 'CVE-2022-23541', 'CVE-2016-20018', 'CVE-2023-0464', 'CVE-2023-0286', 'CVE-2023-0215', 'CVE-2022-4450', 'CVE-2022-0778', 'CVE-2023-0466', 'CVE-2023-0465', 'CVE-2022-4304', 'CVE-2022-2097', 'CVE-2021-4160', 'CVE-2023-22467', 'CVE-2022-31129', 'CVE-2022-24785', 'CVE-2021-23566', 'CVE-2022-35255', 'CVE-2023-23919', 'CVE-2023-23918', 'CVE-2022-43548', 'CVE-2022-32212', 'CVE-2022-21824', 'CVE-2022-0778', 'CVE-2021-44531', 'CVE-2023-23936', 'CVE-2023-23920', 'CVE-2022-35256', 'CVE-2022-32215', 'CVE-2022-32214', 'CVE-2022-32213', 'CVE-2021-44533', 'CVE-2021-44532', 'CVE-2022-24999'] storage: ['CVE-2022-39353', 'GHSA-qm7x-rc44-rrqw', 'GHSA-2p3c-p3qw-69r4', 'CVE-2021-43138', 'CVE-2022-28391', 'CVE-2022-25901', 'CVE-2022-1365', 'CVE-2022-1365', 'CVE-2022-1365', 'CVE-2022-1365', 'CVE-2021-33587', 'CVE-2022-38900', 'CVE-2022-38900', 'CVE-2022-24434', 'CVE-2022-24434', 'GHSA-984p-xq9m-4rjw', 'CVE-2022-36313', 'CVE-2022-0536', 'CVE-2022-0155', 'GHSA-7wwv-vh3v-89cq', 'GHSA-7wwv-vh3v-89cq', 'CVE-2021-20066', 'CVE-2022-46175', 'CVE-2022-46175', 'CVE-2022-23540', 'CVE-2022-23539', 'CVE-2022-23541', 'CVE-2016-20018', 'CVE-2016-20018', 'CVE-2023-0464', 'CVE-2023-0286', 'CVE-2023-0215', 'CVE-2022-4450', 'CVE-2022-0778', 'CVE-2023-0466', 'CVE-2023-0465', 'CVE-2022-4304', 'CVE-2022-2097', 'CVE-2021-4160', 'CVE-2023-22467', 'CVE-2022-21670', 'CVE-2022-21670', 'CVE-2022-3517', 'CVE-2021-44906', 'CVE-2022-31129', 'CVE-2022-24785', 'GHSA-v78c-4p63-2j6c', 'GHSA-56x4-j7p9-fcf9', 'CVE-2021-32036', 'CVE-2019-2386', 'CVE-2019-20925', 'CVE-2017-2665', 'CVE-2021-20333', 'CVE-2020-7929', 'CVE-2020-7928', 'CVE-2020-7921', 'CVE-2019-2393', 'CVE-2019-2392', 'CVE-2019-2389', 'CVE-2018-25004', 'CVE-2018-20805', 'CVE-2018-20804', 'CVE-2018-20803', 'CVE-2018-20802', 'CVE-2014-8180', 'GHSA-2jcg-qqmg-46q6', 'CVE-2021-23566', 'CVE-2022-35255', 'CVE-2023-23919', 'CVE-2023-23918', 'CVE-2022-43548', 'CVE-2022-32212', 'CVE-2022-21824', 'CVE-2022-0778', 'CVE-2021-44531', 'CVE-2023-23936', 'CVE-2023-23920', 'CVE-2022-35256', 'CVE-2022-32215', 'CVE-2022-32214', 'CVE-2022-32213', 'CVE-2021-44533', 'CVE-2021-44532', 'CVE-2022-0235', 'CVE-2020-15168', 'CVE-2022-0235', 'CVE-2022-0235', 'CVE-2022-0235', 'CVE-2022-0235', 'CVE-2022-24772', 'CVE-2022-24771', 'CVE-2022-24773', 'CVE-2022-0122', 'GHSA-gf8q-jrpm-jvxq', 'GHSA-5rrq-pxf6-6jx5', 'CVE-2023-25653', 'CVE-2015-8851', 'CVE-2022-25896', 'CVE-2021-41580', 'CVE-2022-39299', 'CVE-2021-39171', 'CVE-2022-24999', 'CVE-2022-24999', 'CVE-2022-24999', 'CVE-2022-24999', 'CVE-2022-24999', 'CVE-2022-24999', 'CVE-2023-28155', 'CVE-2022-25912', 'CVE-2022-25860', 'CVE-2022-24433', 'CVE-2022-24066', 'CVE-2022-43441', 'CVE-2022-21227', 'CVE-2021-37713', 'CVE-2021-37712', 'CVE-2021-37701', 'CVE-2021-32804', 'CVE-2021-32803', 'CVE-2022-25927', 'CVE-2021-23358', 'CVE-2021-23358', 'CVE-2021-32640', 'CVE-2021-32640', 'CVE-2023-0842', 'CVE-2023-0842', 'CVE-2023-0842', 'CVE-2023-0842', 'CVE-2022-39353', 'CVE-2021-32796', 'CVE-2021-21366']
e2e-test / e2e-test (synchronizer_race_condition)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (synchronizer_proxy)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (synchronizer_reconciliation)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (synchronizer)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (network_policy_data_appended)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (network_policy_multiple_replicas)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (network_policy)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (network_policy_known_servers)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (scan_compliance_score)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (ks_microservice_ns_creation)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (ks_microservice_nsa_and_mitre_framework_demand)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (ks_microservice_mitre_framework_on_demand)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (ks_microservice_update_cronjob_schedule)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (ks_microservice_on_demand)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (vuln_scan_test_public_registry_connectivity_excluded_by_backend)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (vuln_scan_trigger_scan_public_registry_excluded)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (vuln_scan_test_public_registry_connectivity_by_backend)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (vuln_scan_trigger_scan_private_quay_registry)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (vuln_scan_triggering_with_cron_job)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (vuln_scan_trigger_scan_public_registry)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (vuln_scan_proxy)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (relevancy_golang_dynamic)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (relevancy_python)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (relevancy_java)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (relevancy_java_and_python)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (relevancy_golang)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (relevancy_fix_vuln)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (relevancy_extra_large_image)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (relevancy_large_image)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (relevancy_storage_disabled)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (relevancy_enabled_stop_sniffing)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (relevantCVEs)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (relevant_data_is_appended)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (relevancy_disabled_installation)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (registry_scanning_triggering_with_cron_job)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (ks_microservice_triggering_with_cron_job)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (network_policy_pod_restarted)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (ks_microservice_delete_cronjob)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (ks_microservice_create_2_cronjob_mitre_and_nsa)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e-test / e2e-test (ks_microservice_create_2_cronjob_mitre_and_nsa_proxy)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.3.0, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
helm-chart-release
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, azure/setup-helm@v3.5. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
helm-chart-release
Error while fetching latest Helm release: Error: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set. It must be set on either `env:` or `with:`. See https://github.com/octokit/auth-action.js#createactionauth. Using default version v3.9.0