Skip to content

NimTechnology

Trình bày các công nghệ CLOUD một cách dễ hiểu.

  • Kubernetes & Container
    • Docker
    • Kubernetes
      • Ingress
      • Pod
    • Helm Chart
    • OAuth2 Proxy
    • Isito-EnvoyFilter
    • Apache Kafka
      • Kafka
      • Kafka Connect
      • Lenses
    • Vault
    • Longhorn – Storage
    • VictoriaMetrics
    • MetalLB
    • Kong Gateway
  • CI/CD
    • ArgoCD
    • ArgoWorkflows
    • Argo Events
    • Spinnaker
    • Jenkins
    • Harbor
    • TeamCity
    • Git
      • Bitbucket
  • Coding
    • DevSecOps
    • Terraform
      • GCP – Google Cloud
      • AWS – Amazon Web Service
      • Azure Cloud
    • Golang
    • Laravel
    • Python
    • Jquery & JavaScript
    • Selenium
  • Log, Monitor & Tracing
    • DataDog
    • Prometheus
    • Grafana
    • ELK
      • Kibana
      • Logstash
  • BareMetal
    • NextCloud
  • Toggle search form

[Argo-Workflows] Lesson20: Cron Workflow

Posted on April 12, 2023 By nim No Comments on [Argo-Workflows] Lesson20: Cron Workflow

Bạn sẽ cần lập lịch chạy 1 vài flow và argo cũng sẽ hỗ trợ bạn

apiVersion: argoproj.io/v1alpha1
kind: CronWorkflow
metadata:
  name: cronwf-dag
spec:
  schedule: "0 2 * * *"
  concurrentcyPolicy: "Forbid"
  startingDeadLineSeconds: 70
  
  workflowSpec:
    entrypoint: dag-templates
    templates:
    - name: dag-templates
      dag:
        tasks:
        - name: Task1
          template: task-template
        - name: Task2
          template: task-template
          dependencies: [Task1]
        - name: Task3
          template: task-template
          dependencies: [Task1]
        - name: Task4
          template: task-template
          dependencies: [Task2, Task3]

    - name: task-template
      script:
        image: python:3.8-slim
        command: 
        source: |
          print("Nimtechnology - Task executed.")

Chúng ta cùng tìm hiểu 1 chút về pipeline trên.

concurrentcyPolicy: “Forbid” cái này nghĩa là không cho các job chạy đồng thời khi job A chưa xong thì chưa chạy job B ==> nó kiểu như là crontab của là 1 phút chạy 1 lần, nhưng mà job của bạn 2 phút để complete thì nó sẽ chờ job đó chạy xong mới start job mới

StartingDeadlineSeconds is a field in CronWorkflow that specifies the maximum amount of time in seconds that a CronWorkflow can wait for a job to start before it is considered failed. This field is optional, and if it is not specified, the CronWorkflow will wait indefinitely for the job to start.

For example, suppose you have a CronWorkflow that is scheduled to run every hour and triggers a Kubernetes Job. If the StartingDeadlineSeconds field is set to 3600 (1 hour), the CronWorkflow will wait for up to one hour for the Job to start. If the Job has not started within this time frame, the CronWorkflow will be considered failed and will not trigger the Job.

Here is an example of a CronWorkflow YAML manifest that includes the StartingDeadlineSeconds field:

apiVersion: argoproj.io/v1alpha1
kind: CronWorkflow
metadata:
  name: example-cron
spec:
  startingDeadlineSeconds: 1800
  schedule: "*/30 * * * *"
  workflowSpec:
    entrypoint: my-workflow
    templates:
      - name: my-workflow
        container:
          image: my-image
          command: ["/bin/sh"]
          args: ["-c", "echo Hello World"]

In this example, the CronWorkflow is scheduled to run every 30 minutes (*/30 * * * *) and has a startingDeadlineSeconds value of 1800 (30 minutes). If the Kubernetes Job triggered by this CronWorkflow does not start within 30 minutes, the CronWorkflow will be considered failed.

Bạn có thể thao khảo bài này để hiểu thêm về nhiều option.

ArgoWorkflows

Post navigation

Previous Post: [Argo-Workflows] Lesson19: Workflow Template
Next Post: [Argo-Workflows] Lesson22: Reference to Workflow Templates

More Related Articles

[Argo Workflow] Build the docker image with argo-workflow and Kaniko then push the image to ECR ArgoWorkflows
[Argo-Workflows] Lesson10: Loop ArgoWorkflows
[Argo-Workflows] Lesson11: Loops with sets ArgoWorkflows
[Argo-Workflows] Lesson12: Loops with sets as input parameters ArgoWorkflows
[Argo-Workflows] Lesson4: Script result – receive the output result of another task to make the input parameter. ArgoWorkflows
[Argo-Workflows] Lesson17: Retry strategy ArgoWorkflows

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Tham Gia Group DevOps nhé!
Để Nim có nhiều động lực ra nhiều bài viết.
Để nhận được những thông báo mới nhất.

Recent Posts

  • [Azure] The subscription is not registered to use namespace ‘Microsoft.ContainerService’ May 8, 2025
  • [Azure] Insufficient regional vcpu quota left May 8, 2025
  • [WordPress] How to add a Dynamic watermark on WordPress. May 6, 2025
  • [vnet/Azure] VNet provisioning via Terraform. April 28, 2025
  • [tracetcp] How to perform a tracert command using a specific port. April 3, 2025

Archives

  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021

Categories

  • BareMetal
    • NextCloud
  • CI/CD
    • Argo Events
    • ArgoCD
    • ArgoWorkflows
    • Git
      • Bitbucket
    • Harbor
    • Jenkins
    • Spinnaker
    • TeamCity
  • Coding
    • DevSecOps
    • Golang
    • Jquery & JavaScript
    • Laravel
    • NextJS 14 & ReactJS & Type Script
    • Python
    • Selenium
    • Terraform
      • AWS – Amazon Web Service
      • Azure Cloud
      • GCP – Google Cloud
  • Kubernetes & Container
    • Apache Kafka
      • Kafka
      • Kafka Connect
      • Lenses
    • Docker
    • Helm Chart
    • Isito-EnvoyFilter
    • Kong Gateway
    • Kubernetes
      • Ingress
      • Pod
    • Longhorn – Storage
    • MetalLB
    • OAuth2 Proxy
    • Vault
    • VictoriaMetrics
  • Log, Monitor & Tracing
    • DataDog
    • ELK
      • Kibana
      • Logstash
    • Fluent
    • Grafana
    • Prometheus
  • Uncategorized
  • Admin

Copyright © 2025 NimTechnology.