[
https://issues.apache.org/jira/browse/SPARK-26729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcelo Vanzin resolved SPARK-26729.
------------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Issue resolved by pull request 23846
[https://github.com/apache/spark/pull/23846]
> 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
> Fix For: 3.0.0
>
>
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
