-
Notifications
You must be signed in to change notification settings - Fork 241
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
Respect a service's docker_registry for adhoc spark-runs #3728
Conversation
There are some services where we want to ensure that a specialized docker registry is always used - even for adhoc development runs. This change is loosely based on what we do in push-to-registry, where we read service.yaml to see if a specialized registry needs to be used.
registry_uri = args.docker_registry or _get_adhoc_docker_registry( | ||
service=args.service, | ||
soa_dir=args.yelpsoa_config_root, | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the intent here is to allow --docker-registry to override whatever is in yelpsoa
(I tested this locally with the -y flag and verified that by default docker-dev is still used) |
(and that --docker-registry takes precedence over service.yaml) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm.
Would be useful to test once pushed out.
…nd-ckj-aware-of-downthenup-bounces-across-namespaces * origin/master: Update paasta_tools/kubernetes_tools.py Released 0.205.1 via make release Use the correct registry_uri to check if we need to sudo Released 0.205.0 via make release Respect a service's docker_registry for adhoc spark-runs (#3728) Update requirements-dev-minimal.txt Making paasta playground not override existing confs add VSCode debugpy as dev requirement added paasta-crons make target Adding LimitRanges for paasta managed namespaces
There are some services where we want to ensure that a specialized docker registry is always used - even for adhoc development runs.
This change is loosely based on what we do in push-to-registry, where we read service.yaml to see if a specialized registry needs to be used.