[
https://issues.jboss.org/browse/WFWIP-192?page=com.atlassian.jira.plugin....
]
Jeff Mesnil commented on WFWIP-192:
-----------------------------------
[~mchoma] there is no guarantee that the WildFly Operator and EAP Operator will always be
in sync as they move at different pace
Right now, we are working from the wildfly-operator master HEAD but after the first
release, the EAP Operator will be based on releases from the wildfly-operator.
The CRD of the EAP Operator will then be synchronised only when we change the release of
the WildFly Operator we want to productize.
I'll sync the EAP CRD once I fixed the WildFly Operator CRD by change the Size field
to Replicas
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)