Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Task]: Stop using GCR in Beam #31150

Open
1 of 16 tasks
tvalentyn opened this issue May 1, 2024 · 0 comments
Open
1 of 16 tasks

[Task]: Stop using GCR in Beam #31150

tvalentyn opened this issue May 1, 2024 · 0 comments

Comments

@tvalentyn
Copy link
Contributor

What needs to happen?

GCR is deprecated in favor of Google Artifact registry. We use GCR in some integration tests, such as Python ValidatesContainer test, and possibly a few other other places. At some point, GCR might disallow pushing new images.

I looked at some failing ValidatesContainer tests as part of 2.56.0 release validation. I saw tests that exercise prebuilding workflow using the local_docker mode failing: logs said image was pushed, but Dataflow couldn't pull image from GCR. Errors like this wouldn't be investigated sine GCR is deprecated and we should switch to AR.

Issue Priority

Priority: 2 (default / most normal work should be filed as P2)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant