Skip to content

Commit d77303f

Browse files
authored
Revert: whitelist jaeger image from Artifact Hub security scan (#733)
## Reverts #731 The whitelist approach just hides the security vulnerabilities for all users rather than fixing the root cause. The proper fix is to wait for the Jaeger project to release a new image with: - Updated Alpine base (OpenSSL 3.5.5-r0+) - Updated Go stdlib (1.25.6+ or 1.24.12+) Once that happens, we'll update the appVersion and the security rating will improve naturally. Signed-off-by: Jonah Kowall <jkowall@kowall.net>
1 parent b0247f5 commit d77303f

1 file changed

Lines changed: 1 addition & 11 deletions

File tree

charts/jaeger/Chart.yaml

Lines changed: 1 addition & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -3,17 +3,7 @@ appVersion: 2.14.1
33
description: A Jaeger Helm chart for Kubernetes
44
name: jaeger
55
type: application
6-
version: 4.4.4
7-
# Artifact Hub annotations
8-
# The jaeger image is whitelisted from security scanning because the reported
9-
# CVEs are in the upstream Alpine base image (OpenSSL libcrypto3/libssl3) and
10-
# Go stdlib, not in this Helm chart. These will be resolved when the Jaeger
11-
# project releases a new image with updated base packages.
12-
annotations:
13-
artifacthub.io/images: |
14-
- name: jaeger
15-
image: jaegertracing/jaeger:2.14.1
16-
whitelisted: true
6+
version: 4.4.5
177
# CronJobs require v1.21
188
kubeVersion: ">= 1.21-0"
199
keywords:

0 commit comments

Comments
 (0)