Iván Valdés Castillo

@joshjms, why did we decide to drop the `-0` suffix from the image tag? I don't know when or where we had that conversation.

We discussed this in our community meeting on August 21st, 2025. We agreed to push our `etcd:v` image as `registry.k8s.io/etcd:-r0`. As a minimal step to achieve compatibility and push the...

We reviewed this during our bi-weekly triage meeting. The current bill of materials tooling we use is unstable. Ideally, we should prioritize #20303 / #18902 higher.

Do we have access to arm nodes in the Prow infra? The last I remember is that we were waiting for them. I don't see any updates regarding this on...

I can see two options: pause running robustness for the ARM architecture (not ideal) or keep ARM tests running on GitHub actions. I don't see much activity in https://github.com/kubernetes/k8s.io/issues/6102. Who...

Discussed on Slack with Arka, we'll be working on the following at the moment: - Migrate robustness documentation to Prow https://github.com/etcd-io/etcd/tree/main/tests/robustness - Add robustness tests presubmits /assign @ArkaSaha30 @ivanvc

We have finished the first and the third tasks. When would you think is a good time to remove the GitHub action @serathius? We can't move forward with the second,...

@ArkaSaha30, can you help with > Remove non-arm robustness tests from github actions.? Thanks.

@jmhbnz, @serathius, are we ready to remove `optional: true` from the robustness presubmit jobs and mark this issue as complete?

> I don't think we can close this yet though, we still have an problem with the `ci-etcd-robustness-arm64`. Perhaps team at next robustness meeting could take a look at that...