[jboss-jira] [JBoss JIRA] (WFWIP-167) EAP Operator handling ConfigMap internally

[Martin Choma (Jira)]

    [ https://issues.jboss.org/browse/WFWIP-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13769977#comment-13769977 ] 

Martin Choma commented on WFWIP-167:
------------------------------------

This is opening whole new way how to configure EAP in openshift. And rise question how to apply EAP configuration runtime changes. So far applying runtime changes was not the question, because s2i configuration file was applied during building image. 

Is there plan operator will provide way how to apply runtime changes? E.g. rolling update in next phases? Or we are OK with declaring in documentation, that to apply runtime changes user have to restart pods himself.

[~brian.stansberry] I know we have discussed before applying runtime changes is not a question in OpenShift environment . Are you aware we are going to support way how to change EAP configuration in runtime on openshift? Also [~luck3y] wdyt about proposed change?

> EAP Operator handling ConfigMap internally
> ------------------------------------------
>
>                 Key: WFWIP-167
>                 URL: https://issues.jboss.org/browse/WFWIP-167
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: OpenShift
>            Reporter: Martin Choma
>            Assignee: Jeff Mesnil
>            Priority: Major
>
> If I understand description in [1] correctly. To specify custom standalone.xml I have to create ConfigMap with standalone.xml first and afterwards link operator to this ConfigMap.
> Is it possible to handle creation of ConfigMap and storing standalone.xml for me? Ideally I just specify file URI where custom standalone.xml is located. This location have to be accessible from operator pod. In this way we can look at it as hiding internals (implementation details) from users.
> Currently when user wants to change standalone.xml he does in ConfigMap, not operator. When changing standalone.xml through config map, I assume pod have to be restarted manually. Operator could do that for me. 
> However this can be triggered by storing newer version of standalone.xml under another key, eg `standalone.xml.v2` and changing `StandaloneConfigMapSpec.key` in operator.
> What do you think? Have you considered this approach?
> [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#standaloneconfigmapspec



--
This message was sent by Atlassian Jira
(v7.12.1#712002)