Unsupported workflows
Dagweave Local checks every workflow for settings that need a real cluster, and stops if it can’t honour one. To run the check on its own:
dagweave lint my-workflow.yamlA clean workflow prints:
my-workflow.yaml: nothing here needs a cluster feature this machine lacks.Otherwise it prints a refuse or warn line per finding, with the field, its
template and what to do. It exits non-zero if anything is refused.
How a finding is decided
Section titled “How a finding is decided”The check covers the pod spec each step would get, including
spec.templateDefaults and podSpecPatch, plus the workflow, each template and
each lifecycle hook. A refused field stops the run. A warned one runs, with a
note on what differs. A field Dagweave Local has no rule for is refused.
Refused
Section titled “Refused”nodeSelector,affinity,nodeName,runtimeClassName,schedulingGatesandresourceClaims. The step would never start.serviceAccountName. No such account exists locally.resourceandplugintemplates.templateRefandworkflowTemplateRef. There are no stored WorkflowTemplates locally.- A workflow or template that suspends, since nothing can resume it.
- A
{{workflow.*}}variable Dagweave Local can’t supply, or a variable that points at an input, output or step that doesn’t exist. - A
when,dependsor{{=...}}that Argo can’t parse, or that reads an input, output or step that doesn’t exist or hasn’t run yet. Test an expression withdagweave expr.
Warned
Section titled “Warned”- An expression that reads a workflow parameter
spec.argumentsdoesn’t declare. It only has a value if you pass it with-p. imagePullSecrets,hostPathvolumes and persistent volume claims.- CPU and memory limits. On the host, nothing enforces them.
hostNetwork,hostPIDandhostIPC. They point at the local cluster’s container, not your laptop.synchronizationandmemoize. No locks are held and nothing is cached.metrics. Nothing collects them.- On the host only:
activeDeadlineSecondson the workflow or a template, andparallelismlimits.
A warning about a Secret goes away once you store it with
dagweave secret.
Ignored
Section titled “Ignored”Scheduling settings that mean nothing on one node, such as tolerations,
priorityClassName, topologySpreadConstraints, podDisruptionBudget and
resource requests.
Steps that run kubectl or helm
Section titled “Steps that run kubectl or helm”The check can’t see what a kubectl or helm command will do. Five catalog
steps are refused, with their reason: helm-upgrade, kubectl-apply, kubectl-delete,
scale-deployment and wait-for-rollout.
Your own steps run as the default service account in the local cluster’s argo
namespace. It can create, get and patch pods, and create and get workflows,
there. Anything else, such as a Deployment or a Secret, fails on permissions.
Watch out for kubectl apply. A Pod or Workflow applied to argo lands in the
local cluster and the step succeeds, but nothing reaches the cluster you meant.