[jboss-jira] [JBoss JIRA] (WFWIP-198) EAP Operator long-term strategy

[ https://issues.jboss.org/browse/WFWIP-198?page=com.atlassian.jira.plugin.... ] Martin Choma edited comment on WFWIP-198 at 9/17/19 8:39 AM: ------------------------------------------------------------- [~jmesnil] I have in mind customers which need transactions, but need configure Openshift in way Operator does not support. When critical feature as transaction will be available only throught Operator they will be locked-in. As customers are creative, I expect customers will come with requests for RFEs to expose internal kubernetes object parameters. And we will actually end in state exposing most of internal objects through Operator anyway. [~ochaloup] What about these customers who can't/don't want to use operator but do need transactions? Jeff could you formulate clear EAP operator contract which will be communicated to customers. So far seems to me it is something like this: - Operator does not provides all capabilities that working directly with Kubernetes objects do. And never will. - Operator provides opinionated way how to configure Kubernetes environment for runing EAP. Not all ways. - You cant touch internal Kubernetes objects created by Operator to change setting. Operator will overwrite your changes. - If you need something what Operator does not provide you can raise RFE for operator or turn off operator and be on your own. - Transactions are supported only when using Operator was (Author: mchoma): [~jmesnil] I have in mind customers which need transactions, but need configure Openshift in way Operator does not support. When critical feature as transaction will be available only throught Operator they will be locked-in. As customers are creative, I expect customers will come with requests for RFEs to expose internal kubernetes object parameters. And we will actually end in state exposing most of internal objects through Operator anyway. [~ochaloup] What about these customers who can't/don't want to use operator but do need transactions? Could you formulate clear EAP operator contract which will be communicated to customers. So far seems to me it is something like this: - Operator does not provides all capabilities that working directly with Kubernetes objects do. And never will. - Operator provides opinionated way how to configure Kubernetes environment for runing EAP. Not all ways. - You cant touch internal Kubernetes objects created by Operator to change setting. Operator will overwrite your changes. - If you need something what Operator does not provide you can raise RFE for operator or turn off operator and be on your own. - Transactions are supported only when using Operator -- This message was sent by Atlassian Jira (v7.13.5#713005)