<div dir="ltr">Hi José,<div> When the project first started, OpenShift Templates was the only way to deploy.</div><div>Now that we have (or about to have) DaemonSets, we no longer need to use</div><div>OpenShift Templates.</div><div><br></div><div>- Luis</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 30, 2016 at 7:16 PM, Jose A. Rivera <span dir="ltr"><<a href="mailto:jarrpa@redhat.com" target="_blank">jarrpa@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Heyo,<br>
<br>
Naturally, as soon as I upload OpenShift support for the gk-deploy<br>
script, I find myself wondering: why do we have templates for heketi<br>
for OpenShift? Specifically, why do we create Template objects instead<br>
of the direct objects (e.g. Service, DeploymentConfig)? Do we have a<br>
need for the ability to recreate heketi pods with different parameters<br>
within the same namespace? We live without them in Kubernetes, and at<br>
present even with Templates the deployment of heketi in OpenShift is<br>
not much easier for a sysadmin if at all.<br>
<br>
--Jose<br>
<br>
P.S. This all comes as I'm trying to bring a DaemonSet GlusterFS to<br>
OpenShift. ;)<br>
______________________________<wbr>_________________<br>
heketi-devel mailing list<br>
<a href="mailto:heketi-devel@gluster.org">heketi-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/heketi-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/heketi-devel</a><br>
</blockquote></div><br></div>