Skip to content

Conversation

@spicerabot
Copy link
Contributor

@spicerabot spicerabot bot commented Oct 29, 2025

This PR contains the following updates:

Package Update Change
ghcr.io/kiwigrid/k8s-sidecar major 1.30.11 -> 2.1.2

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

kiwigrid/k8s-sidecar (ghcr.io/kiwigrid/k8s-sidecar)

v2.1.2

Compare Source

📦 Dependencies
  • Bump mikepenz/release-changelog-builder-action from 6.0.0 to 6.0.1
  • Bump docker/setup-qemu-action from 3.6.0 to 3.7.0
  • Bump fastapi from 0.115.2 to 0.121.0 in /src

v2.1.1

Compare Source

📦 Dependencies
  • Bump mikepenz/release-changelog-builder-action from 6.0.0 to 6.0.1
  • Bump docker/setup-qemu-action from 3.6.0 to 3.7.0
  • Bump fastapi from 0.115.2 to 0.121.0 in /src

v2.1.0

Compare Source

🚀 Features
  • wyn_skip_init: - add flag to skip initial request to REQ_URL when using WATCH
📦 Dependencies
  • Bump actions/upload-artifact from 4 to 5
  • Bump actions/download-artifact from 5 to 6

v2.0.3

Compare Source

Build
Enhancements
  • Add health endpoint with readiness and liveness probes (#​416)

  • New /healthz Endpoint: A new HTTP endpoint is available on port 8080 (configurable via the HEALTH_PORT environment variable)

    • Readiness Probe:

      • The sidecar now reports as "ready" (HTTP 200) only after the initial synchronization of all configured resources is complete
      • This prevents the main application container from starting or receiving traffic prematurely, ensuring all configuration files are present at startup
    • Liveness Probe:

      • The probe continuously monitors the sidecar's health by checking two critical conditions:
        • Kubernetes API Contact: Verifies that the sidecar has had successful contact with the Kubernetes API within the last 60 seconds
        • Watcher Process Health: Ensures that all internal watcher subprocesses are running correctly
      • If any check fails, the probe fails, signaling Kubernetes to restart the container
  • Reduced Log Noise: Access logs for frequent /healthz requests are automatically filtered out to keep application logs clean and focused

  • Fail-Fast on Process Death: The main process now exits immediately if a critical watcher subprocess dies, ensuring a prompt restart by Kubernetes

Testing
  • The CI pipeline has been enhanced with new tests to validate this functionality:
    • A test to confirm the Uvicorn health server starts successfully
    • A liveness test that simulates a watcher process failure and asserts that Kubernetes restarts the pod as expected
    • A Kubernetes Config load test for Sleep and Watch based sidecar

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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 these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@spicerabot spicerabot bot requested a review from spiceratops as a code owner October 29, 2025 08:12
@spicerabot spicerabot bot force-pushed the renovate/ghcr.io-kiwigrid-k8s-sidecar-2.x branch 25 times, most recently from ced6062 to 3206e57 Compare November 3, 2025 16:13
@spicerabot spicerabot bot force-pushed the renovate/ghcr.io-kiwigrid-k8s-sidecar-2.x branch 23 times, most recently from eceb477 to cebe7f6 Compare November 22, 2025 21:12
@spicerabot spicerabot bot force-pushed the renovate/ghcr.io-kiwigrid-k8s-sidecar-2.x branch 5 times, most recently from 0322591 to beea567 Compare November 24, 2025 00:39
@spicerabot spicerabot bot force-pushed the renovate/ghcr.io-kiwigrid-k8s-sidecar-2.x branch from beea567 to 24eb641 Compare November 24, 2025 02:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants