Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-15632

Zookeeper HA service could not work for active kubernetes integration

    XMLWordPrintableJSON

    Details

      Description

      It will be some different, if we want to support HA for active Kubernetes integration.

      1. The K8s service is designed for accessing the jobmanager out of K8s cluster. So Flink client will not use HA service to retrieve address of jobmanager. Instead, it always use Kubernetes service to contact with jobmanager via rest client. 
      2. The Kubernetes DNS creates A and SRV records only for Services. It doesn't generate pods' A records. So the ip address, not hostname, will be used as jobmanager address.

       

      All other behaviors will be same as Zookeeper HA for standalone and Yarn.

      To fix this problem, we just need some minor changes to KubernetesClusterDescriptor and KubernetesSessionEntrypoint.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                fly_in_gis Yang Wang
                Reporter:
                fly_in_gis Yang Wang
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m