3 Replies Latest reply on Nov 4, 2019 8:33 AM by GREGOIRE Alain

    Clustered application in Kubernetes

    GREGOIRE Alain Newbie

      Hi,

       

      I'm looking for example of WF clustered application running inside Kubernetes.

      Does anybody handle this ?

      Is it possible to share configuration or example with me ?

       

      Regards.

        • 2. Re: Clustered application in Kubernetes
          GREGOIRE Alain Newbie

          Thank you for your answer ; I will test it ASAP.

          • 3. Re: Clustered application in Kubernetes
            GREGOIRE Alain Newbie

            Hi,

             

            I tested your solution and I'm still facing to SessionId issue (I'm forcing the refresh of the page)

             

                <stack name="tcp">

                    <transport type="TCP" socket-binding="jgroups-tcp"/>

                        <protocol type="kubernetes.KUBE_PING">

                            <property name="namespace">gregoan-dev-namespace</property>

                            <property name="labels">cluster=nyc</property>

                        </protocol>

                ...

             

            The Kubernetes configuration looks fine :

             

             

                kubectl --kubeconfig /ec/local/automation/repos/git_repos/toolingautomation_ans_core/conf/kubernetes/config_nonprod_digit_c2_child get all --namespace gregoan-dev-namespace

             

                NAME                                          READY   STATUS    RESTARTS   AGE

                pod/gregoan-dev-deployment-5cd47b9456-bmqfw   1/1     Running   0          35m

                pod/gregoan-dev-deployment-5cd47b9456-jrvd5   1/1     Running   0          34m

             

                NAME                          TYPE           CLUSTER-IP      EXTERNAL-IP                                                                       PORT(S)                                        AGE

                service/gregoan-dev-service   LoadBalancer   172.20.35.215   internal-aaf07de61fee011e994940a8660df4f7-896756341.eu-west-1.elb.amazonaws.com   8080:30933/TCP,8443:31239/TCP,9990:31200/TCP   4h21m

             

                NAME                                     READY   UP-TO-DATE   AVAILABLE   AGE

                deployment.apps/gregoan-dev-deployment   2/2     2            2           4h21m

             

                NAME                                                DESIRED   CURRENT   READY   AGE

                replicaset.apps/gregoan-dev-deployment-5cd47b9456   2         2         2       35m

             

            The "Label" element is well optional ?

            Did I miss something ?

             

            Regards.