Kubernetes Jobs & Cronjobs | How it works

Поделиться
HTML-код
  • Опубликовано: 21 ноя 2024

Комментарии • 9

  • @adityahpatel
    @adityahpatel 9 месяцев назад +1

    I have a question - Running 10 pods in parallel isn't going to help. What will help is running 10 pods where each Pod is processing a DIFFERENT batch/slice of data. How to do that?

  • @jac6963
    @jac6963 Год назад

    Nicely explained

  • @deepakranjanmishra5641
    @deepakranjanmishra5641 Год назад

    Very Nice Explanation Sir

  • @niteshb4832
    @niteshb4832 Год назад

    Good and simple explanation

  • @dipalibadadhe8930
    @dipalibadadhe8930 Год назад

    Very nice to explain and good guidance👍👏👏

  • @dadasahebkale880
    @dadasahebkale880 Год назад

    Good Explanation

  • @AbhayAR
    @AbhayAR 11 месяцев назад

    what if i want my pod should be terminated automatically and spin up when cron job starts

    • @techworldwithrajendra
      @techworldwithrajendra  11 месяцев назад

      Here pod does not terminate and will re mail in completed state for some time and will be removed after some time. New pod will be created for next cron job trigger

    • @AbhayAR
      @AbhayAR 11 месяцев назад

      @@techworldwithrajendra But in my case pod is being completed, we have cron job and what is happening, when job starts, will create a new pod, once it finish next day at 7 it is completed, again when cron starts, it will spin a new pod, technically it should terminate the previous one,
      any suggestion on ttlsecondsafterfinished?