You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2019/03/20 21:29:00 UTC
[jira] [Assigned] (SPARK-26729) Spark on Kubernetes tooling
hardcodes default image names
[ https://issues.apache.org/jira/browse/SPARK-26729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcelo Vanzin reassigned SPARK-26729:
--------------------------------------
Assignee: Rob Vesse
> Spark on Kubernetes tooling hardcodes default image names
> ---------------------------------------------------------
>
> Key: SPARK-26729
> URL: https://issues.apache.org/jira/browse/SPARK-26729
> Project: Spark
> Issue Type: Improvement
> Components: Kubernetes
> Affects Versions: 2.4.0
> Reporter: Rob Vesse
> Assignee: Rob Vesse
> Priority: Major
>
> Both when creating images with {{bin/docker-image-tool.sh}} and when running the Kubernetes integration tests the image names are hardcoded to {{spark}}, {{spark-py}} and {{spark-r}}.
> If you are producing custom images in some other way (e.g. a CI/CD process that doesn't use the script) or are required to use a different naming convention due to company policy e.g. prefixing with vendor name (e.g. {{apache-spark}}) then you can't directly create/test your images with the desired names.
> You can of course simply re-tag the images with the desired names but this might not be possible in some CI/CD pipelines especially if naming conventions are being enforced at the registry level.
> It would be nice if the default image names were customisable
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org