Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-17709 Active Kubernetes integration phase 3 - Advanced Features
  3. FLINK-15641

Support to start init container

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • None
    • None
    • Deployment / Kubernetes
    • 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

        Issue Links

          duplicates

          Sub-task - The sub-task of the issue FLINK-15656 Support user-specified pod templates

          • Major - Major loss of function.
          • Closed
          relates to

          Sub-task - The sub-task of the issue FLINK-15656 Support user-specified pod templates

          • Major - Major loss of function.
          • Closed
          links to

          Web Link Support init container and sidecar container

          Activity

            People

              Unassigned Unassigned
              wangyang0918 Yang Wang
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: