Closed blazs3fs closed 8 months ago
I know the argument names are fixed strings but currently there is no other way to detect these to images. Maybe we could find a way to automatically check if the arguments change in the helm template of the kube-prometheus-stack
project.
@blazs3fs, I'll check both the referenced issues and the changes made by you on helm-images and get back to you.
Hi @nikhilsbhat! Did you have any time to check my PR? I could also split the build fixes into a separate PR if that makes things any easier?
@blazs3fs , I'm on a long leave, mostly I will be back next week. I'll check this out once I'm back.
Reason for PR
helm-images
does not recognize theprometheus-config-reloader
andthanos
images provided via container arguments. This PR adds and additional check and append the additional images to the final output.I've first tried to resolve this issue with the
kube-prometheus-stack
maintainers and they also opened an issue withartifact.hub
but unfortunately it was closed. More about the discussion can be read here and here.Other fixes
When I tried building the project with the
make local.build
command failed and after some investigation on howgoreleaser
works I've also implemented some build process fixes. Please see commits for details.Test procedure for container image extraction fix
Download
kube-prometheus-stack
and extract it (not the newest version, but this is the one I tested with)Extract images without fix
Extract images with fix (I am using an ARM based Mac, so I chose the
darwin_arm64
binary)Observe these additional extracted images
quay.io/prometheus-operator/prometheus-config-reloader:v0.68.0
quay.io/thanos/thanos:v0.32.4