[jboss-jira] [JBoss JIRA] (WFWIP-215) Operator headless service labeled with wildfly.org/operated-by-loadbalancer=active

[Martin Choma (Jira)]

     [ https://issues.jboss.org/browse/WFWIP-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Choma closed WFWIP-215.
------------------------------


I can verify issue is not present in image-registry.openshift-image-registry.svc:5000/eapcd-suite-builds/jboss-eap-7-tech-preview-eap-operator:jb-eap-7.3-operator-rhel8-containers-candidate-66988-20191001135536

> Operator headless service labeled with wildfly.org/operated-by-loadbalancer=active
> ----------------------------------------------------------------------------------
>
>                 Key: WFWIP-215
>                 URL: https://issues.jboss.org/browse/WFWIP-215
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: OpenShift
>            Reporter: Martin Choma
>            Assignee: Ondrej Chaloupka
>            Priority: Blocker
>
> # create the WildflyServer CR 
> {code:yaml}
> apiVersion: wildfly.org/v1alpha1
> kind: WildFlyServer
> metadata:
>   name: eap-cd
>   namespace: mchoma
> spec:
>   applicationImage: >-
>     image-registry.openshift-image-registry.svc:5000/eapcd-suite-builds/eap-cd-openshift-rhel8:17.0-4
>   env: []
>   envFrom: []
>   size: 1
> {code}
> # Both services {{eap-cd-headless}} and {{eap-cd-loadbalancer}} created by Operator have same labels. We used to select service based on label wildfly.org/operated-by-loadbalancer.  
> {code}
> eap-cd-headless
> app.kubernetes.io/managed-by=eap-operator
> app.kubernetes.io/name=eap-cd
> app.openshift.io/runtime=eap
> wildfly.org/operated-by-loadbalancer=active
> eap-cd-loadbalancer
> app.kubernetes.io/managed-by=eap-operator
> app.kubernetes.io/name=eap-cd
> app.openshift.io/runtime=eap
> wildfly.org/operated-by-loadbalancer=active
> {code}



--
This message was sent by Atlassian Jira
(v7.13.8#713008)