Open rhuss opened 8 years ago
Has any work been done on this? looking in the source can't see any mentions of io.fabric8.openshift.api.model.TemplateBuilder, which i used with the v2 plugin
FWIW gofabric8 installs things as kubernetes templates.
We could have a plugin configuration to force the openshift.yml to be converted to an OpenShift template. I guess it depends if openshift users ever choose to go with helm which supports install, upgrade & delete - rather than just install
This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!
This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!
You're such a pain,stalebot
At the moment on plain Kubernetes objects are created. When running in OpenShift mode the template handling should be introduced.
In contrast to the old implementation where the template is created first and then, if pure Kubernetes objects are requested, the template is applied locally and objects from non-Kubernetes packages are removed, the discrimination template yes/no should be done from the very beginning.
Also it could make sense that even for OpenShift non-template can be created.
The idea is to have an
OpenShiftConfiguration
object, inherited fromKubernetesKonfiguration
and stored in a memberopenshift
, so that the discrimnation happens based on the top-level configuration tagvs
with
useTemplates == true
being the default. (useTemplates
is then also only available for<openshift>