Closed NotChristianGarcia closed 1 year ago
Settled on accessing Pod templates with pod_template: "template/neoj"
and pod_template: "template/postgres"
. Regular user images no longer require specifying the additional custom-
. For example, users now can use pod_template: "jstubbs/abaco_test"
rather than the more complicated pod_template: "custom-jstubbs/abaco_test"
,
Currently specify images as:
neo4j
custom-jstubbs/abaco_test
Ideas for solutions:
pod-templates/neo4j
could be the new way to specify using a template. Let's just reserve pod-templates on dockerhub and understand in the service that pod-templates actually means to run our code.jstubbs/abaco_test
as you would expect.Harder to make adding templates easier. Templates could be turned into a dictionary of values to use. Hard though when we have to create custom credentials per pod or run whatever arbitrary code that's required to run the template. Possible though.
Could also have regex parse the
kubernetes_templates.py
file, find functions,start_neo4j_pod
, and parse just the image name. This might be the easier way.