[ https://issues.jboss.org/browse/WFWIP-198?page=com.atlassian.jira.plugin.... ] Martin Choma edited comment on WFWIP-198 at 9/16/19 2:39 AM: ------------------------------------------------------------- So if I understand you correctly you are saying your preference is 2. Problem is EAP7-1192 wont permit turn off operator for people using transaction. So when user find himself in situation he need option which Operator does not expose, he will raise RFE and wait couple of months to be delivered. I assume over a time customers will come with request to expose nearly all internal Kubernetes objects options. Which will mean Operator will expose all options, but that will be in your words "disaster from a usability and maintenance point of view". And I agree. "we need to make sure that the Operator is able to do all the things that we currently support" Now the question is how we define "we". - Is it just what EAP document and test? - Or also what OpenShift document and test? For example EAP do not document neither test pod.spec.imagePullSecrets option. It is documented by OpenShift documentation so supported by RedHat. So should we add this option to Operator in this stage? [1] https://docs.openshift.com/container-platform/3.11/rest_api/api/v1.Pod.html was (Author: mchoma): So if I understand you correctly you are saying your preference is 2. Problem is EAP7-1192 wont permit turn off operator for people using transaction. So when user find himself in situation he need option which Operator does not expose, he will raise RFE and wait couple of months to be delivered. I assume over a time customers will come with request to expose nearly all internal Kubernetes objects options. Which will mean Operator will expose all options, but that will be in your words "disaster from a usability and maintenance point of view". And I agree. "we need to make sure that the Operator is able to do all the things that we currently support" Now the question is how we define "we". - Is it just what EAP document and test? - Or also what OpenShift document and test? For example EAP do not document neither test pod.spec.imagePullSecrets option. It is documented by OpenShift documentation so supported by RedHat. So should we add this option to Operator in this stage? [1] https://docs.openshift.com/container-platform/3.11/rest_api/api/v1.Pod.html -- This message was sent by Atlassian Jira (v7.13.5#713005)