Deprecations¶
Sometimes a feature of Argo Workflows is deprecated. You should stop using a deprecated feature as it may be removed in a future minor or major release of Argo Workflows.
To determine if you are using a deprecated feature the deprecated_feature metric can help.
This metric will go up for each use of a deprecated feature by the workflow controller.
This means it may go up once or many times for a single event.
If the number is going up the feature is still in use by your system.
If the metric is not present or no longer increasing are no longer using the monitored deprecated features.
cronworkflow schedule¶
The spec field schedule which takes a single value is replaced by schedules which takes a list.
To update this replace the schedule with schedules as in the following example
spec:
schedule: "30 1 * * *"
is replaced with
spec:
schedules:
- "30 1 * * *"
synchronization mutex¶
The synchronization field mutex which takes a single value is replaced by mutexes which takes a list.
To update this replace mutex with mutexes as in the following example
synchronization:
mutex:
name: foobar
is replaced with
synchronization:
mutexes:
- name: foobar
synchronization semaphore¶
The synchronization field semaphore which takes a single value is replaced by semaphores which takes a list.
To update this replace semaphore with semaphores as in the following example
synchronization:
semaphore:
configMapKeyRef:
name: my-config
key: workflow
is replaced with
synchronization:
semaphores:
- configMapKeyRef:
name: my-config
key: workflow
workflow podpriority¶
The Workflow spec field podPriority which takes a numeric value is deprecated and podPriorityClassName should be used instead.
To update this you will need a PriorityClass in your cluster and refer to that using podPriorityClassName.