Update quay.io/coreos/etcd Docker tag to v3.7.1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
quay.io/coreos/etcd	service	minor	v3.5.15 → v3.7.1
quay.io/coreos/etcd		minor	v3.5.21 → v3.7.1

---

Configuration

📅 Schedule: (UTC)

• 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 was generated by Mend Renovate. View the repository job log.

[greptile-apps]

PR author is in the excluded authors list.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: eb93f98276

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Keep etcd log filter tag aligned with service image

After changing the service image to quay.io/coreos/etcd:v3.6.8, the failure handler in the Wait for etcd step still runs docker ps -q --filter ancestor=quay.io/coreos/etcd:v3.5.15 (line 277), so when readiness fails it will not match the running container and emits no etcd logs. This regresses CI diagnosability exactly in the scenario where logs are needed most (startup/health failures).

Useful? React with 👍 / 👎.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 1a91463b-e039-4b25-a3f6-2d65d272be14

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch renovate/quay.io-coreos-etcd-3.x

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch renovate/quay.io-coreos-etcd-3.x

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[kilo-code-bot]

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Fix these issues in Kilo Cloud

Issue Details (click to expand)

WARNING

File	Line	Issue
.github/workflows/ci.yml	302	The Wait for etcd failure path still filters docker ps by quay.io/coreos/etcd:v3.5.15, so the updated v3.6.13 service container will not be matched when readiness fails and CI will omit the logs needed to diagnose startup failures.

Files Reviewed (2 files)

• .github/workflows/ci.yml - 1 issue
• docker-compose.yml - no issues

Previous Review Summaries (2 snapshots, latest commit 03cd8cd)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit 03cd8cd)

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Fix these issues in Kilo Cloud

Issue Details (click to expand)

WARNING

File	Line	Issue
.github/workflows/ci.yml	302	The Wait for etcd failure path still filters docker ps by quay.io/coreos/etcd:v3.5.15, so the updated v3.6.13 service container will not be matched when readiness fails and CI will omit the logs needed to diagnose startup failures.

Files Reviewed (2 files)

• .github/workflows/ci.yml - 1 issue
• docker-compose.yml - no issues

Previous review (commit b41a6f4)

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	2
SUGGESTION	0

Fix these issues in Kilo Cloud

Issue Details (click to expand)

No new inline-commentable issues. The CI log-filter mismatch is already covered by an existing review comment, and the remaining version-drift finding is outside the diff.

Other Observations (not in diff)

Issues found outside changed diff hunks that cannot receive inline comments:

File	Line	Issue
.github/workflows/ci.yml	302	The Wait for etcd failure path still filters docker ps by quay.io/coreos/etcd:v3.5.15, so if the v3.6.12 container fails to become ready CI will no longer print the etcd logs needed to diagnose the failure.
crates/gossip-coordination-etcd/src/test_support.rs	80	etcd_image() still provisions quay.io/coreos/etcd:v3.5.15, so testcontainers-backed integration runs exercise a different etcd version than CI and docker-compose.yml; the version references in crates/gossip-coordination-etcd/src/tests.rs:20, crates/gossip-coordination-etcd/src/test_support.rs:114, and docs/gossip-coordination/coordination-testing.md:24 are stale for the same reason.

Files Reviewed (5 files)

• .github/workflows/ci.yml - 1 warning
• docker-compose.yml - no issues
• crates/gossip-coordination-etcd/src/test_support.rs - 1 warning
• crates/gossip-coordination-etcd/src/tests.rs - context only
• docs/gossip-coordination/coordination-testing.md - context only

---

_{Reviewed by gpt-5.5-2026-04-23 · Input: 37K · Output: 3.9K · Cached: 125.4K}