Hi everyone, As part of the work done to migrate the GitHub Actions runners over to GKE, the, not exhaustive, changes below were performed:
- added a new secret to the apache-beam-testing project (this is the PAT needed by the docker image to connect to GitHub) - added a new docker image (which will execute the test flows still being ran by GitHub) and other changes which you can take a look at here: https://github.com/apache/beam/pull/15039/files Among those, the ones of notice are the following: - .github/workflows/build_wheels.yml - .github/workflows/cancel.yml - .github/workflows/java_tests.yml - .github/workflows/python_tests.yml - .test-infra/metrics/build.gradle - .test-infra/metrics/build_and_publish_containers.sh - .test-infra/metrics/docker-compose.yml - .test-infra/metrics/kubernetes/beamgrafana-deploy.yaml - .test-infra/metrics/sync/githubactions/Dockerfile - .test-infra/metrics/sync/githubactions/entrypoint.sh The docker image (.test-infra/metrics/sync/githubactions/Dockerfile) has been built and pushed to the GCP container registry already. Now, I need to deploy the new docker image to GKE. I've done that before, but in a testing cluster/namespace. I'd definitely feel more comfortable if someone knowledgeable with the Apache Beam Testing project GKE architecture watches over my shoulder. I think I have everything covered, but I could be missing some important piece. Thanks for the help! -- *This email and its contents (including any attachments) are being sent to you on the condition of confidentiality and may be protected by legal privilege. Access to this email by anyone other than the intended recipient is unauthorized. If you are not the intended recipient, please immediately notify the sender by replying to this message and delete the material immediately from your system. Any further use, dissemination, distribution or reproduction of this email is strictly prohibited. Further, no representation is made with respect to any content contained in this email.*
