[jboss-jira] [JBoss JIRA] (WFWIP-192) Sync eap CRD with wildfly CRD
[
https://issues.jboss.org/browse/WFWIP-192?page=com.atlassian.jira.plugin....
]
Martin Choma commented on WFWIP-192:
------------------------------------
Yeah I mean. We release wildfly-operator, e.g {{1.0}} and say we want to productize to
eap-operator {{1.0}}. In that case CRD of wildfly-operator and eap-operator will be same,
right? This is guaranteed?
So I understand sync is now manual step. That mean error prone. So someone should check.
Will that be checked during productization? Or should we check? Sometimes our testsuite
can reveal error in CRD, but this is not 100%
For sure best would be to have sync fully automated (if possible) so eap-operator gets
always same CRD as wildfly-operator which he is based on. What do you think?
Sync eap CRD with wildfly CRD
-----------------------------
Key: WFWIP-192
URL: https://issues.jboss.org/browse/WFWIP-192
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Martin Choma
Assignee: Jeff Mesnil
Priority: Major
Comparing wildfly and eap CRD revealed differences
{code}
wget
https://raw.githubusercontent.com/wildfly/wildfly-operator/master/deploy/...
-O wildfly_operator_crd
wget
https://raw.githubusercontent.com/jbossas/eap-operator-packaging/prototyp...
-O eap_operator_crd
diff wildfly_operator_crd eap_operator_crd
{code}
{code}
36,37d35
< disableHTTPRoute:
< type: boolean
50,53d47
< sessionAffinity:
< description: SessionAffinity defines if connections from the same
client
< ip are passed to the same WildFlyServer instance/pod each time
< type: boolean
79,82d72
< hosts:
< items:
< type: string
< type: array
94a85,86
> required:
> - pods
{code}
Please sync so we can test against.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)