Handling OpenShift templates

[aweiteka]

OpenShift templates can be instantiated two ways for different use cases.

1. oc create -f <template>: this uploads the template to openshift. This might be an end-user or it might be an admin pre-loading templates for all users by passing in -n openshift. This does not actually create any resources; just makes the app template available for parameterized instantiation. Creating an app from a template can be done from CLI or web UI. No params are parsed or required when creating or uploading a template.
2. oc new-app ...: this creates an application. If a template is supplied then the params required params must be passed in using --param=foo=bar. This would be done by an end-user.

Use case 1 feels like template installation. Use case 2 is analogous to running or starting an application.

So how should we handle these two use-cases? When a template is run should we require params every time using new-app? If so, how can we handle uploading a template, use case 1? atomic install really cannot be used for this as it's currently implemented.

[goern]

I would say we focus on use case 2. given the vision of Nulecule to configure and deploy applications, the first use cases feels like out of scope. Acknowledging that there may be the need to deploy a template to be used as such, we should push this back and invent a mechanism to deploy unprocessed artifacts to a provider.

[cdrage]

@aweiteka with #278 as well as the kubernetes config passthrough command, are we safely able to implement this now?

[aweiteka]

with #278 as well as the kubernetes config passthrough command, are we safely able to implement this now?

@charliedrage I don't think there was anything blocking this work. It may work as desired. I need to review how things work today with templates and see if it matches use case 2.