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

[Martin Choma (Jira)]

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

Martin Choma commented on WFWIP-198:
------------------------------------

[~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

> EAP Operator long-term strategy
> -------------------------------
>
>                 Key: WFWIP-198
>                 URL: https://issues.jboss.org/browse/WFWIP-198
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: OpenShift
>            Reporter: Martin Choma
>            Assignee: Jeff Mesnil
>            Priority: Blocker
>
> Facts:
> # Operator creates and manges internaly several kubernetes objects; StatefulSet, Pod, Service, Routes. By rough estimation these kubernetes objects expose approximately 50 options[2]. Operator now expose approximately 10 options [1].
> # EAP7-1192 is currently designed in way operator is integral part of solution. You can not turn off operator to EAP7-1192 properly work.
> # User cant touch internal Kubernetes objects. Operator manages them and can overwrite changes anytime.
> So given these facts question is what is long-term strategy with Operator?
> # Operator will provide all options of internal objects. Everything I am able to configure directly with Kubernetes objects I will be able to configure with Operator
> # Operator will expose just most useful options. If user wants to make something special he has to "turn off" operator and to be on his own. (Loosing transaction support provided by EAP7-1192)
> # Operator will expose just most useful options. If user wants to make something special he can and Operator won't overwritten his changes. (I dont know if it is feasible?)
> [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#wildflyserverspec
> [2]
> https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#podspec-v1-core
> https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#statefulsetspec-v1beta1-apps
> https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#servicespec-v1-core
> https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#ingressspec-v1beta1-networking-k8s-io



--
This message was sent by Atlassian Jira
(v7.13.5#713005)