Repository navigation
feat(container)!: Update image ghcr.io/home-operations/charts/gatus-sidecar (0.4.1 ➔ 0.5.1) - #7419
Conversation
drag0n141-bot
Bot
added
renovate/container
type/minor
area/kubernetes
--- kubernetes/apps/monitoring/gatus-sidecar/app Kustomization: monitoring/gatus-sidecar OCIRepository: monitoring/gatus-sidecar
+++ kubernetes/apps/monitoring/gatus-sidecar/app Kustomization: monitoring/gatus-sidecar OCIRepository: monitoring/gatus-sidecar
@@ -11,9 +11,9 @@
spec:
interval: 15m
layerSelector:
mediaType: application/vnd.cncf.helm.chart.content.v1.tar+gzip
operation: copy
ref:
- tag: 0.4.1
+ tag: 0.5.1
url: oci://ghcr.io/home-operations/charts/gatus-sidecar
|
--- HelmRelease: monitoring/gatus-sidecar Deployment: monitoring/gatus-sidecar
+++ HelmRelease: monitoring/gatus-sidecar Deployment: monitoring/gatus-sidecar
@@ -43,13 +43,13 @@
- envFrom:
- secretRef:
name: gatus-sidecar-secret
image: ghcr.io/home-operations/postgres-init:18
name: init-db
- name: gatus-sidecar
- image: ghcr.io/home-operations/gatus-sidecar@sha256:e6470515bc63a714d1d4630761f72b4bc5be775aad6e09be4becb11505fae38e
+ image: ghcr.io/home-operations/gatus-sidecar@sha256:221084ee862aecfa95b7797c66a4578e47a0bd08ea2c173fd6814a58e556b319
imagePullPolicy: IfNotPresent
restartPolicy: Always
args:
- --output=/config/gatus-sidecar.yaml
- --default-interval=1m
- --probe-paths=true |
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
gatus-sidecar chart: v0.4.1 → v0.5.0
Verdict: Safe to merge
This is the home-operations/gatus-sidecar chart+app (same repo, bundled release). Bumps in the diff:
- Bug fix: excludes example comments from unrelated chart schema descriptions
- Dependency bump:
k8s.iomonorepo v0.36.3 → v0.36.4 - Breaking (upstream):
fix(resources)!: fully qualify Service endpoint hostnames(#175) — for auto-discoveredkind: Serviceendpoints, the sidecar now emits<service>.<namespace>.svc.<cluster-domain>.(absolute, trailing dot) instead of<service>.<namespace>.svc, using a new--cluster-domainflag (chart valueclusterDomain, defaultcluster.local). The upstream author explicitly calls out this will break setups where the cluster's real DNS domain differs fromcluster.localandclusterDomainis left unset.
Impact assessment:
kubernetes/apps/monitoring/gatus-sidecar/app/helmrelease.yamldoes not setclusterDomain, so it uses the sidecar's default (cluster.local).talos/machineconfig.yaml.j2setsdnsDomain: cluster.local, and the coredns HelmRelease is configured forcluster.local— confirmed the cluster's actual domain matches the default, so the new FQDN resolution will work correctly.- Only one
kind: Servicegatus endpoint exists in this repo (kubernetes/apps/networking/smtp-relay/app/helmrelease.yaml,service.app.annotations["gatus.home-operations.com/endpoint"]). It'll now resolve assmtp-relay.networking.svc.cluster.local.instead ofsmtp-relay.networking.svc— functionally equivalent here, and per the upstream rationale, marginally more efficient DNS resolution (avoids an NXDOMAIN root-server round trip before the search-list match). All othergatus.home-operations.comannotations in the repo are on HTTPRoute/Gateway resources, which are unaffected by this change.
No action required before merging.
Sources consulted:
…idecar (0.4.1 ➔ 0.5.1)
62767dd to
34a5254
Compare
drag0n141-bot
Bot
changed the title
There was a problem hiding this comment.
gatus-sidecar chart: v0.5.0 → v0.5.1 (this PR now spans v0.4.1 → v0.5.1)
Verdict: Safe to merge
This PR was previously reviewed at v0.4.1 → v0.5.0 (approved, no action required). It has since been updated to target v0.5.1. The only change in that delta:
fix(go): update to go 1.27.0(#177) — a Go toolchain bump for the sidecar binary, no application-level behavior change.
No new breaking changes, deprecations, or features were introduced between 0.5.0 and 0.5.1.
Re-verified the previously-flagged breaking change (fix(resources)!: fully qualify Service endpoint hostnames, introduced in 0.5.0) still holds safe in the current repo state: clusterDomain remains unset in kubernetes/apps/monitoring/gatus-sidecar/app/helmrelease.yaml (defaults to cluster.local), and talos/machineconfig.yaml.j2 still sets dnsDomain: cluster.local, so the new FQDN resolution is a no-op functionally. Note the scope of affected kind: Service gatus endpoints is broader than previously counted — in addition to smtp-relay, the following also carry gatus.home-operations.com/endpoint annotations directly on Service objects: postgres-lb, postgres-vector-lb, postgres-timescale-lb (cloudnative-pg), and the Dragonfly-managed service (serviceSpec.annotations). All resolve under the matching cluster.local domain, so this remains a non-issue.
No action required before merging.
Sources consulted:
This PR contains the following updates:
0.4.1→0.5.1Release Notes
home-operations/gatus-sidecar (ghcr.io/home-operations/charts/gatus-sidecar)
v0.5.1Compare Source
Bug Fixes
v0.5.0Compare Source
⚠ BREAKING CHANGES
Bug Fixes
Documentation
Configuration
📅 Schedule: (in timezone Europe/Berlin)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.