Automated Prometheus version update 0.93.0-88.3.0 - #6061
Automated Prometheus version update 0.93.0-88.3.0#6061replicated-ci-kurl wants to merge 2 commits into
Conversation
|
Reviews (1): Last reviewed commit: "Create new Prometheus version" | Re-trigger Greptile |
| # change ClusterIP services to NodePorts if required | ||
| if [ -z "$PROMETHEUS_SERVICE_TYPE" ] || [ "$PROMETHEUS_SERVICE_TYPE" = "NodePort" ] ; then | ||
| cp "$src/nodeport-services.yaml" "$operatordst" | ||
| insert_patches_strategic_merge "$operatordst/kustomization.yaml" nodeport-services.yaml |
There was a problem hiding this comment.
NodePort Patch Uses Legacy Kustomize Field
When PROMETHEUS_SERVICE_TYPE is unset or NodePort, this new version appends nodeport-services.yaml through insert_patches_strategic_merge. On clusters whose kubectl apply -k uses a kustomize version that rejects or mishandles patchesStrategicMerge, the Prometheus apply can fail before the operator resources are recreated, leaving the upgrade without the expected monitoring services.
d724ad7 to
9989b06
Compare
|
Reviews (2): Last reviewed commit: "Create new Prometheus version" | Re-trigger Greptile |
9989b06 to
5ca55f8
Compare
|
Reviews (3): Last reviewed commit: "Create new Prometheus version" | Re-trigger Greptile |
5ca55f8 to
5e0cb68
Compare
|
Reviews (4): Last reviewed commit: "Create new Prometheus version" | Re-trigger Greptile |
5e0cb68 to
12d11bb
Compare
|
Reviews (5): Last reviewed commit: "Create new Prometheus version" | Re-trigger Greptile |
|
Reviews (6): Last reviewed commit: "empty commit to trigger CI" | Re-trigger Greptile |
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-6061-f1d6a86-prometheus-0.93.0-88.3.0-k8s-docker-2026-08-17T23:10:10Z |
Automated changes by the cron-prometheus-update GitHub action