Argo Workflows website screenshot

Argo Workflows

Argo Workflows is an open-source, container-native workflow engine for orchestrating parallel jobs on Kubernetes. It is a CNCF graduated project that allows you to define workflows where each step is a container, model multi-step workflows as sequences of tasks or DAGs, and run compute-intensive jobs for machine learning, data processing, and CI/CD pipelines natively on Kubernetes. Governed by the Linux Foundation and the CNCF.

1 APIs 12 Features
CNCFContainersData ProcessingKubernetesMachine LearningOpen SourceWorkflow Engine

APIs

Argo Workflows API

The Argo Workflows REST API provides programmatic access to workflow lifecycle management, workflow templates, cron scheduling, archived workflow history, events, and cluster wo...

Collections

Pricing Plans

Rate Limits

Argo Workflows Rate Limits

5 limits

RATE LIMITS

FinOps

Features

Container-Native Workflows

Every workflow step runs as a Kubernetes container, providing complete isolation and reproducibility.

DAG and Step-Based Orchestration

Define multi-step workflows as sequential steps or directed acyclic graphs (DAGs) with dependencies.

Parallel Execution

Run multiple workflow steps in parallel to maximize compute utilization and reduce execution time.

Workflow Templates

Store and reuse workflow definitions as templates across the cluster.

Cron Workflows

Schedule workflows to run on cron schedules directly on Kubernetes.

Artifact Support

Pass artifacts between workflow steps via S3, GCS, Azure Blob, Artifactory, and more.

Workflow Archive

Persist workflow history to a database for long-term retention and querying.

Web UI

Monitor and manage workflows through a rich graphical interface.

Multi-Tenancy

Namespace-based isolation with RBAC for multi-team environments.

Event-Driven Triggers

Trigger workflows from Kubernetes events, webhooks, and custom event sources.

Python SDK (Hera)

Define workflows in Python using the Hera SDK, the official Python SDK.

Plugin Architecture

Extend with custom executor plugins and artifact driver plugins.

Use Cases

Machine Learning Pipelines

Orchestrate data preparation, model training, evaluation, and deployment as containerized steps.

Data Processing and ETL

Run parallel data transformation and ETL jobs at scale on Kubernetes.

CI/CD on Kubernetes

Run CI/CD pipelines natively on Kubernetes without external CI tools.

Batch Processing

Process large datasets in parallel with automatic resource management.

Infrastructure Automation

Automate infrastructure provisioning, testing, and validation workflows.

Scientific Computing

Orchestrate complex scientific computation and simulation jobs with dependencies.

Integrations

Python Hera SDK

Official Python SDK for defining and submitting workflows programmatically.

Argo CD

Use Argo CD to deploy and manage Argo Workflows resources via GitOps.

Prometheus

Expose workflow metrics for Prometheus monitoring and alerting.

Grafana

Visualize workflow performance metrics in Grafana dashboards.

HashiCorp Vault

Inject secrets into workflow containers securely via Vault integration.

Amazon S3

Use S3 as artifact storage for passing data between workflow steps.

Google GCS

Use Google Cloud Storage as artifact backend.

Azure Blob Storage

Use Azure Blob Storage for artifact persistence.

Kubeflow

Run Kubeflow ML pipelines using Argo Workflows as the underlying engine.

Apache Spark

Orchestrate Apache Spark jobs as Argo Workflow steps.

Semantic Vocabularies

Argo Workflows Eventsource Context

6 classes · 10 properties

JSON-LD

Argo Workflows Github Context

122 classes · 361 properties

JSON-LD

Argo Workflows Google Context

1 classes · 2 properties

JSON-LD

Argo Workflows Grpc Context

2 classes · 7 properties

JSON-LD

Argo Workflows Io Context

281 classes · 611 properties

JSON-LD

Argo Workflows Sensor Context

6 classes · 12 properties

JSON-LD

Argo Workflows Sync Context

4 classes · 5 properties

JSON-LD

API Governance Rules

Argo Workflows API Rules

13 rules · 5 errors 6 warnings 2 info

SPECTRAL

JSON Structure

Argo Workflows Google Protobuf Any Structure

2 properties

JSON STRUCTURE

Argo Workflows Sensor Log Entry Structure

8 properties

JSON STRUCTURE

Example Payloads

Resources

🔗
LinkedIn
LinkedIn
🔗
Website
Website
🔗
Documentation
Documentation
🚀
GettingStarted
GettingStarted
👥
GitHubOrganization
GitHubOrganization
👥
GitHubRepository
GitHubRepository
📄
ReleaseNotes
ReleaseNotes
📄
ChangeLog
ChangeLog
🔗
CLI
CLI
📦
SDKs
SDKs
💬
Support
Support
🔗
SpectralRules
SpectralRules
🔗
Vocabulary
Vocabulary

Sources

Raw ↑
opencollection: 1.0.0
info:
  name: Argo Workflows
  version: 3.6.0
items:
- info:
    name: ArchivedWorkflowService
    type: folder
  items:
  - info:
      name: ArchivedWorkflowService_ListArchivedWorkflows
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/api/v1/archived-workflows'
      params:
      - name: listOptions.labelSelector
        value: ''
        type: query
        description: 'A selector to restrict the list of returned objects by their labels.

          Defaults to everything.

          +optional.'
      - name: listOptions.fieldSelector
        value: ''
        type: query
        description: 'A selector to restrict the list of returned objects by their fields.

          Defaults to everything.

          +optional.'
      - name: listOptions.watch
        value: ''
        type: query
        description: 'Watch for changes to the described resources and return them as a stream of

          add, update, and remove notifications. Specify resourceVersion.

          +optional.'
      - name: listOptions.allowWatchBookmarks
        value: ''
        type: query
        description: 'allowWatchBookmarks requests watch events with type "BOOKMARK".

          Servers that do not implement bookmarks may ignore this flag and

          bookmarks are sent at the server''s discretion. Clients should not

          assume bookmarks are returned at any specific interval, nor may they

          assume the server will send any BOOKMARK event during a session.

          If this is not a watch, this field is ignored.

          +optional.'
      - name: listOptions.resourceVersion
        value: ''
        type: query
        description: 'resourceVersion sets a constraint on what resource versions a request may be served from.

          See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for

          details.


          Defaults to unset

          +optional'
      - name: listOptions.resourceVersionMatch
        value: ''
        type: query
        description: 'resourceVersionMatch determines how resourceVersion is applied to list calls.

          It is highly recommended that resourceVersionMatch be set for list calls where

          resourceVersion is set

          See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for

          details.


          Defaults to unset

          +optional'
      - name: listOptions.timeoutSeconds
        value: ''
        type: query
        description: 'Timeout for the list/watch call.

          This limits the duration of the call, regardless of any activity or inactivity.

          +optional.'
      - name: listOptions.limit
        value: ''
        type: query
        description: 'limit is a maximum number of responses to return for a list call. If more items exist, the

          server will set the `continue` field on the list metadata to a value that can be used with the

          same initial query to retrieve the next set of results. Setting a limit may return fewer than

          the requested amount of items (up to zero items) in the event all requested objects are

          filtered out and clients should only use the presence of the continue field to determine whether

          more results are available. Servers may choose not to support the limit argument and will return

          all of the available results. If limit is specified and the continue field is empty, clients may

          assume that no more results are available. This field is not supported if watch is true.


          The server guarantees that the objects returned when using continue will be identical to issuing

          a single list call without a limit - that is, no objects created, modified, or deleted after the

          first request is issued will be included in any subsequent continued requests. This is sometimes

          referred to as a consistent snapshot, and ensures that a client that is using limit to receive

          smaller chunks of a very large result can ensure they see all possible objects. If objects are

          updated during a chunked list the version of the object that was present at the time the first list

          result was calculated is returned.'
      - name: listOptions.continue
        value: ''
        type: query
        description: 'The continue option should be set when retrieving more results from the server. Since this value is

          server defined, clients may only use the continue value from a previous query result with identical

          query parameters (except for the value of continue) and the server may reject a continue value it

          does not recognize. If the specified continue value is no longer valid whether due to expiration

          (generally five to fifteen minutes) or a configuration change on the server, the server will

          respond with a 410 ResourceExpired error together with a continue token. If the client needs a

          consistent list, it must restart their list without the continue field. Otherwise, the client may

          send another list request with the token received with the 410 error, the server will respond with

          a list starting from the next key, but from the latest snapshot, which is inconsistent from the

          previous list results - objects that are created, modified, or deleted after the first list request

          will be included in the response, as long as their keys are after the "next key".


          This field is not supported when watch is true. Clients may start a watch from the last

          resourceVersion value returned by the server and not miss any modifications.'
      - name: listOptions.sendInitialEvents
        value: ''
        type: query
        description: "`sendInitialEvents=true` may be set together with `watch=true`.\nIn that case, the watch stream will\
          \ begin with synthetic events to\nproduce the current state of objects in the collection. Once all such\nevents\
          \ have been sent, a synthetic \"Bookmark\" event  will be sent.\nThe bookmark will report the ResourceVersion (RV)\
          \ corresponding to the\nset of objects, and be marked with `\"io.k8s.initial-events-end\": \"true\"` annotation.\n\
          Afterwards, the watch stream will proceed as usual, sending watch events\ncorresponding to changes (subsequent to\
          \ the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch`\noption\
          \ to also be set. The semantic of the watch request is as following:\n- `resourceVersionMatch` = NotOlderThan\n\
          \  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send\
          \ when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n\
          \  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when\
          \ the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch`\
          \ set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or\
          \ `resourceVersion=\"0\"` (for backward\ncompatibility reasons) and to false otherwise.\n+optional"
      - name: namePrefix
        value: ''
        type: query
      - name: namespace
        value: ''
        type: query
      - name: nameFilter
        value: ''
        type: query
        description: Filter type used for name filtering. Exact | Contains | Prefix. Default to Exact.
  - info:
      name: ArchivedWorkflowService_ListArchivedWorkflowLabelKeys
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/api/v1/archived-workflows-label-keys'
      params:
      - name: namespace
        value: ''
        type: query
  - info:
      name: ArchivedWorkflowService_ListArchivedWorkflowLabelValues
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/api/v1/archived-workflows-label-values'
      params:
      - name: listOptions.labelSelector
        value: ''
        type: query
        description: 'A selector to restrict the list of returned objects by their labels.

          Defaults to everything.

          +optional.'
      - name: listOptions.fieldSelector
        value: ''
        type: query
        description: 'A selector to restrict the list of returned objects by their fields.

          Defaults to everything.

          +optional.'
      - name: listOptions.watch
        value: ''
        type: query
        description: 'Watch for changes to the described resources and return them as a stream of

          add, update, and remove notifications. Specify resourceVersion.

          +optional.'
      - name: listOptions.allowWatchBookmarks
        value: ''
        type: query
        description: 'allowWatchBookmarks requests watch events with type "BOOKMARK".

          Servers that do not implement bookmarks may ignore this flag and

          bookmarks are sent at the server''s discretion. Clients should not

          assume bookmarks are returned at any specific interval, nor may they

          assume the server will send any BOOKMARK event during a session.

          If this is not a watch, this field is ignored.

          +optional.'
      - name: listOptions.resourceVersion
        value: ''
        type: query
        description: 'resourceVersion sets a constraint on what resource versions a request may be served from.

          See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for

          details.


          Defaults to unset

          +optional'
      - name: listOptions.resourceVersionMatch
        value: ''
        type: query
        description: 'resourceVersionMatch determines how resourceVersion is applied to list calls.

          It is highly recommended that resourceVersionMatch be set for list calls where

          resourceVersion is set

          See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for

          details.


          Defaults to unset

          +optional'
      - name: listOptions.timeoutSeconds
        value: ''
        type: query
        description: 'Timeout for the list/watch call.

          This limits the duration of the call, regardless of any activity or inactivity.

          +optional.'
      - name: listOptions.limit
        value: ''
        type: query
        description: 'limit is a maximum number of responses to return for a list call. If more items exist, the

          server will set the `continue` field on the list metadata to a value that can be used with the

          same initial query to retrieve the next set of results. Setting a limit may return fewer than

          the requested amount of items (up to zero items) in the event all requested objects are

          filtered out and clients should only use the presence of the continue field to determine whether

          more results are available. Servers may choose not to support the limit argument and will return

          all of the available results. If limit is specified and the continue field is empty, clients may

          assume that no more results are available. This field is not supported if watch is true.


          The server guarantees that the objects returned when using continue will be identical to issuing

          a single list call without a limit - that is, no objects created, modified, or deleted after the

          first request is issued will be included in any subsequent continued requests. This is sometimes

          referred to as a consistent snapshot, and ensures that a client that is using limit to receive

          smaller chunks of a very large result can ensure they see all possible objects. If objects are

          updated during a chunked list the version of the object that was present at the time the first list

          result was calculated is returned.'
      - name: listOptions.continue
        value: ''
        type: query
        description: 'The continue option should be set when retrieving more results from the server. Since this value is

          server defined, clients may only use the continue value from a previous query result with identical

          query parameters (except for the value of continue) and the server may reject a continue value it

          does not recognize. If the specified continue value is no longer valid whether due to expiration

          (generally five to fifteen minutes) or a configuration change on the server, the server will

          respond with a 410 ResourceExpired error together with a continue token. If the client needs a

          consistent list, it must restart their list without the continue field. Otherwise, the client may

          send another list request with the token received with the 410 error, the server will respond with

          a list starting from the next key, but from the latest snapshot, which is inconsistent from the

          previous list results - objects that are created, modified, or deleted after the first list request

          will be included in the response, as long as their keys are after the "next key".


          This field is not supported when watch is true. Clients may start a watch from the last

          resourceVersion value returned by the server and not miss any modifications.'
      - name: listOptions.sendInitialEvents
        value: ''
        type: query
        description: "`sendInitialEvents=true` may be set together with `watch=true`.\nIn that case, the watch stream will\
          \ begin with synthetic events to\nproduce the current state of objects in the collection. Once all such\nevents\
          \ have been sent, a synthetic \"Bookmark\" event  will be sent.\nThe bookmark will report the ResourceVersion (RV)\
          \ corresponding to the\nset of objects, and be marked with `\"io.k8s.initial-events-end\": \"true\"` annotation.\n\
          Afterwards, the watch stream will proceed as usual, sending watch events\ncorresponding to changes (subsequent to\
          \ the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch`\noption\
          \ to also be set. The semantic of the watch request is as following:\n- `resourceVersionMatch` = NotOlderThan\n\
          \  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send\
          \ when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n\
          \  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when\
          \ the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch`\
          \ set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or\
          \ `resourceVersion=\"0\"` (for backward\ncompatibility reasons) and to false otherwise.\n+optional"
      - name: namespace
        value: ''
        type: query
  - info:
      name: ArchivedWorkflowService_GetArchivedWorkflow
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/api/v1/archived-workflows/:uid'
      params:
      - name: uid
        value: ''
        type: path
      - name: namespace
        value: ''
        type: query
      - name: name
        value: ''
        type: query
  - info:
      name: ArchivedWorkflowService_DeleteArchivedWorkflow
      type: http
    http:
      method: DELETE
      url: '{{baseUrl}}/api/v1/archived-workflows/:uid'
      params:
      - name: uid
        value: ''
        type: path
      - name: namespace
        value: ''
        type: query
      - name: name
        value: ''
        type: query
  - info:
      name: ArchivedWorkflowService_ResubmitArchivedWorkflow
      type: http
    http:
      method: PUT
      url: '{{baseUrl}}/api/v1/archived-workflows/:uid/resubmit'
      params:
      - name: uid
        value: ''
        type: path
  - info:
      name: ArchivedWorkflowService_RetryArchivedWorkflow
      type: http
    http:
      method: PUT
      url: '{{baseUrl}}/api/v1/archived-workflows/:uid/retry'
      params:
      - name: uid
        value: ''
        type: path
- info:
    name: ClusterWorkflowTemplateService
    type: folder
  items:
  - info:
      name: ClusterWorkflowTemplateService_ListClusterWorkflowTemplates
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/api/v1/cluster-workflow-templates'
      params:
      - name: listOptions.labelSelector
        value: ''
        type: query
        description: 'A selector to restrict the list of returned objects by their labels.

          Defaults to everything.

          +optional.'
      - name: listOptions.fieldSelector
        value: ''
        type: query
        description: 'A selector to restrict the list of returned objects by their fields.

          Defaults to everything.

          +optional.'
      - name: listOptions.watch
        value: ''
        type: query
        description: 'Watch for changes to the described resources and return them as a stream of

          add, update, and remove notifications. Specify resourceVersion.

          +optional.'
      - name: listOptions.allowWatchBookmarks
        value: ''
        type: query
        description: 'allowWatchBookmarks requests watch events with type "BOOKMARK".

          Servers that do not implement bookmarks may ignore this flag and

          bookmarks are sent at the server''s discretion. Clients should not

          assume bookmarks are returned at any specific interval, nor may they

          assume the server will send any BOOKMARK event during a session.

          If this is not a watch, this field is ignored.

          +optional.'
      - name: listOptions.resourceVersion
        value: ''
        type: query
        description: 'resourceVersion sets a constraint on what resource versions a request may be served from.

          See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for

          details.


          Defaults to unset

          +optional'
      - name: listOptions.resourceVersionMatch
        value: ''
        type: query
        description: 'resourceVersionMatch determines how resourceVersion is applied to list calls.

          It is highly recommended that resourceVersionMatch be set for list calls where

          resourceVersion is set

          See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for

          details.


          Defaults to unset

          +optional'
      - name: listOptions.timeoutSeconds
        value: ''
        type: query
        description: 'Timeout for the list/watch call.

          This limits the duration of the call, regardless of any activity or inactivity.

          +optional.'
      - name: listOptions.limit
        value: ''
        type: query
        description: 'limit is a maximum number of responses to return for a list call. If more items exist, the

          server will set the `continue` field on the list metadata to a value that can be used with the

          same initial query to retrieve the next set of results. Setting a limit may return fewer than

          the requested amount of items (up to zero items) in the event all requested objects are

          filtered out and clients should only use the presence of the continue field to determine whether

          more results are available. Servers may choose not to support the limit argument and will return

          all of the available results. If limit is specified and the continue field is empty, clients may

          assume that no more results are available. This field is not supported if watch is true.


          The server guarantees that the objects returned when using continue will be identical to issuing

          a single list call without a limit - that is, no objects created, modified, or deleted after the

          first request is issued will be included in any subsequent continued requests. This is sometimes

          referred to as a consistent snapshot, and ensures that a client that is using limit to receive

          smaller chunks of a very large result can ensure they see all possible objects. If objects are

          updated during a chunked list the version of the object that was present at the time the first list

          result was calculated is returned.'
      - name: listOptions.continue
        value: ''
        type: query
        description: 'The continue option should be set when retrieving more results from the server. Since this value is

          server defined, clients may only use the continue value from a previous query result with identical

          query parameters (except for the value of continue) and the server may reject a continue value it

          does not recognize. If the specified continue value is no longer valid whether due to expiration

          (generally five to fifteen minutes) or a configuration change on the server, the server will

          respond with a 410 ResourceExpired error together with a continue token. If the client needs a

          consistent list, it must restart their list without the continue field. Otherwise, the client may

          send another list request with the token received with the 410 error, the server will respond with

          a list starting from the next key, but from the latest snapshot, which is inconsistent from the

          previous list results - objects that are created, modified, or deleted after the first list request

          will be included in the response, as long as their keys are after the "next key".


          This field is not supported when watch is true. Clients may start a watch from the last

          resourceVersion value returned by the server and not miss any modifications.'
      - name: listOptions.sendInitialEvents
        value: ''
        type: query
        description: "`sendInitialEvents=true` may be set together with `watch=true`.\nIn that case, the watch stream will\
          \ begin with synthetic events to\nproduce the current state of objects in the collection. Once all such\nevents\
          \ have been sent, a synthetic \"Bookmark\" event  will be sent.\nThe bookmark will report the ResourceVersion (RV)\
          \ corresponding to the\nset of objects, and be marked with `\"io.k8s.initial-events-end\": \"true\"` annotation.\n\
          Afterwards, the watch stream will proceed as usual, sending watch events\ncorresponding to changes (subsequent to\
          \ the RV) to objects watched.\n\nWhen `sendInitialEvents` option is set, we require `resourceVersionMatch`\noption\
          \ to also be set. The semantic of the watch request is as following:\n- `resourceVersionMatch` = NotOlderThan\n\
          \  is interpreted as \"data at least as new as the provided `resourceVersion`\"\n  and the bookmark event is send\
          \ when the state is synced\n  to a `resourceVersion` at least as fresh as the one provided by the ListOptions.\n\
          \  If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the\n  bookmark event is send when\
          \ the state is synced at least to the moment\n  when request started being processed.\n- `resourceVersionMatch`\
          \ set to any other value or unset\n  Invalid error is returned.\n\nDefaults to true if `resourceVersion=\"\"` or\
          \ `resourceVersion=\"0\"` (for backward\ncompatibility reasons) and to false otherwise.\n+optional"
  - info:
      name: ClusterWorkflowTemplateService_CreateClusterWorkflowTemplate
      type: http
    http:
      method: POST
      url: '{{baseUrl}}/api/v1/cluster-workflow-templates'
  - info:
      name: ClusterWorkflowTemplateService_LintClusterWorkflowTemplate
      type: http
    http:
      method: POST
      url: '{{baseUrl}}/api/v1/cluster-workflow-templates/lint'
  - info:
      name: ClusterWorkflowTemplateService_GetClusterWorkflowTemplate
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/api/v1/cluster-workflow-templates/:name'
      params:
      - name: name
        value: ''
        type: path
      - name: getOptions.resourceVersion
        value: ''
        type: query
        description: 'resourceVersion sets a constraint on what resource versions a request may be served from.

          See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for

          details.


          Defaults to unset

          +optional'
  - info:
      name: ClusterWorkflowTemplateService_UpdateClusterWorkflowTemplate
      type: http
    http:
      method: PUT
      url: '{{baseUrl}}/api/v1/cluster-workflow-templates/:name'
      params:
      - name: name
        value: ''
        type: path
        description: 'DEPRECATED: This field is ignored.'
  - info:
      name: ClusterWorkflowTemplateService_DeleteClusterWorkflowTemplate
      type: http
    http:
      method: DELETE
      url: '{{baseUrl}}/api/v1/cluster-workflow-templates/:name'
      params:
      - name: name
        value: ''
        type: path
      - name: deleteOptions.gracePeriodSeconds
        value: ''
        type: query
        description: 'The duration in seconds before the object should be deleted. Value must be non-negative integer.

          The value zero indicates delete immediately. If this value is nil, the default grace period for the

          specified type will be used.

          Defaults to a per object value if not specified. zero means delete immediately.

          +optional.'
      - name: deleteOptions.preconditions.uid
        value: ''
        type: query
        description: 'Specifies the target UID.

          +optional.'
      - name: deleteOptions.preconditions.resourceVersion
        value: ''
        type: query
        description: 'Specifies the target ResourceVersion

          +optional.'
      - name: deleteOptions.orphanDependents
        value: ''
        type: query
        description: 'Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7.

          Should the dependent objects be orphaned. If true/false, the "orphan"

          finalizer will be added to/removed from the object''s finalizers list.

          Either this field or PropagationPolicy may be set, but not both.

          +optional.'
      - name: deleteOptions.propagationPolicy
        value: ''
        type: query
        description: 'Whether and how garbage collection will be performed.

          Either this field or OrphanDependents may be set, but not both.

          The default policy is decided by the existing finalizer set in the

          metadata.finalizers and the resource-specific default policy.

          Acceptable values are: ''Orphan'' - orphan the dependents; ''Background'' -

          allow the garbage collector to delete the dependents in the background;

          ''Foreground'' - a cascading policy that deletes all dependents in the

          foreground.

          +optional.'
      - name: deleteOptions.dryRun
        value: ''
        type: query
        description: 'When present, indicates that modifications should not be

          persisted. An invalid or unrecognized dryRun directive will

          result in an error response and no further processing of the

          request. Valid values are:

          - All: all dry run stages will be processed

          +optional

          +listType=atomic.'
      - name: deleteOptions.ignoreStoreReadErrorWithClusterBreakingPotential
        value: ''
        type: query
        description: 'if set to true, it will trigger an unsafe deletion of the resource in

          case the normal deletion flow fails with a corrupt object error.

          A resource is considered corrupt if it can not be retrieved from

          the underlying storage successfully because of a) its data can

          not be transformed e.g. decryption failure, or b) it fails

          to decode into an object.

          NOTE: unsafe deletion ignores finalizer constraints, skips

          precondition checks, and removes the object from the storage.

          WARNING: This may potentially break the cluster if the workload

          associated with the resource being unsafe-deleted relies on normal

          deletion flow. Use only if you REALLY know what you are doing.

          The default value is false, and the user must opt in to enable it

          +optional.'
- info:
    name: CronWorkflowService
    type: folder
  items:
  - info:
      name: CronWorkflowService_ListCronWorkflows
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/api/v1/cron-workflows/:namespace'
      params:
      - name: namespace
        value: ''
        type: path
      - name: listOptions.labelSelector
        value: ''
        type: query
        description: 'A selector to restrict the list of returned objects by their labels.

          Defaults to everything.

          +optional.'
      - name: listOptions.fieldSelector
        value: ''
        type: query
        description: 'A selector to restrict the list of returned objects by their fields.

          Defaults to everything.

          +optional.'
      - name: listOptions.watch
        value: ''
        type: query
        description: 'Watch for changes to the described resources and return them as a stream of

          add, update, and remove notifications. Specify resourceVersion.

          +optional.'
      - name: listOptions.allowWatchBookmarks
        value: ''
        type: query
        description: 'allowWatchBookmarks requests watch events with type "BOOKMARK".

          Servers that do not implement bookmarks may ignore this flag and

          bookmarks are sent at the server''s discretion. Clients should not

          assume bookmarks are returned at any specific interval, nor may they

          assume the server will send any BOOKMARK event during a session.

          If this is not a watch, this field is ignored.

          +optional.'
      - name: listOptions.resourceVersion
        value: ''
        type: query
        description: 'resourceVersion sets a constraint on what resource versions a request may be served from.

          See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for

          details.


          Defaults to unset

          +optional'
      - name: listOptions.resourceVersionMatch
        value: ''
        type: query
        description: 'resourceVersionMatch determines how resourceVersion is applied to list calls.

          It is highly recommended that resourceVersionMatch be set for list calls where

          resourceVersion is set

          See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for

          details.


          Defaults to unset

          +optional'
      - name: listOptions.timeoutSeconds
        value: ''
        type: query
        description: 'Timeout for the list/watch call.

          This limits the duration of the call, regardless of any activity or inactivity.

          +optional.'
      - name: listOptions.limit
        value: ''
        type: query
        description: 'limit is a maximum number of responses to return for a list call. If more items exist, the

          server will set the `continue` field on the list metadata to a value that can be used with the

          same initial query to retrieve the next set of results. Setting a limit may return fewer than

          the requested amount of items (up to zero items) in the event all requested objects are

          filtered out and clients should only use the presence of the continue field to determine whether

          more results are available. Servers may choose not to support the limit argument and will return

          all of the available results. If limit is specified and the continue field is empty, clients may

          assume that no more results are available. This field is not supported if watch is true.


          The server guarantees that the objects returned when using continue will be identical to issuing

          a single list call without a limit - that is, no objects created, modified, or deleted after the

   

# --- truncated at 32 KB (151 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/argo-workflows/refs/heads/main/apis.yml