Details

    • Type: Sub-task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      >> Why do we need init container?

      The init container could be used to prepare the use jars and dependencies. Then we could always set the user image to Flink official image both for standalone per-job on K8s or native K8s per-job. When the JobManager and TaskManager container launched, the user jars will already exist there. I think many users are running standalone per-job cluster in production by using this way.

      The init container only works for K8s cluster.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated: