Hi everyone! Following up on my intro from earlier. I've been digging deeper into the CI/CD: Kubernetes Integration Testing project today. What I've explored so far: Read through the existing QA test suite at github.com/saikonen/metaflow-qa-tests and understood how the current tests are structured Went through the Metaflow Dev Stack docs — I see it uses Kind + Argo Workflows to spin up a local Kubernetes environment Read the Runner and Deployer API docs — I understand tests should be triggered programmatically through these rather than the CLI directly • While setting up locally on Windows, I hit

ModuleNotFoundError: No module named 'fcntl'

in

metaflow/sidecar/sidecar_subprocess.py

line 4 — traced it to an unconditional Unix-only import, related to #2981. Planning to open a fix for this as my pre-application PR. My background relevant to this project: • 3 years at SAP building and maintaining CI/CD pipelines, backend workflows with Python, REST APIs • Experience with Docker, and familiar with Kubernetes concepts • Currently pursuing MS CS at Texas A&M My questions for @square-wire-39606 and @dry-beach-38304: 1. Are there any gsoc-tagged issues you'd recommend as a good starter PR for someone targeting this project? 2. For the GitHub Actions workflow goal — is the expectation to extend the existing QA test suite or write new tests from scratch? Looking forward to your guidance! — Rishitha