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

[flink-operator] Kubernetes HA Service not working with standalone mode

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      Since flink-conf.yaml is mounted as read-only configmap, the /docker-entrypoint.sh script is not able to inject correct Pod IP to `jobmanager.rpc.address`. This leads to same address (e.g flink.ns-ext) being set for all Job Manager pods. This causes:
      Setting up FlinkDeployment in Standalone mode with Kubernetes HA Service. Problems:

      (1) flink-cluster-config-map always contains wrong address for all 3 component leaders (see screenshot, should be pod IP instead of clusterIP service name)

      (2) Accessing Web UI when jobmanager.replicas > 1 is not possible with error

      {"errors":["Service temporarily unavailable due to an ongoing leader election. Please refresh."]} 

       

      ~ flinkdeployment.yaml ~

      spec:
        mode: standalone
        flinkConfiguration:
          high-availability: kubernetes
          high-availability.storageDir: "file:///opt/flink/storage"
          ...
        jobManager:
          replicas: 3
        ... 

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            usamj Usamah Jassat
            tbnguyen1407 Binh-Nguyen Tran
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment