You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: