mvaictl workload stop¶
Stop a workload
Synopsis¶
Puts the given workload on hold. The workload will not be admitted and if it is already admitted it will be put back to queue just as if it was preempted (using .spec.active field).
If the workload has checkpoint enabled (via label 'memverge.ai/checkpoint-mode' in the associated owners' pod metadata), the workload will be automatically checkpointed.
Examples¶
Options¶
--allow-missing-template-keys If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. (default true)
--dry-run string Must be "none", "server", or "client". If client strategy, only print the object that would be sent, without sending it. If server strategy, submit server-side request without persisting the resource. (default "none")
-h, --help help for stop
-o, --output string Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
--show-managed-fields If true, keep the managedFields when printing objects in JSON or YAML format.
--template string Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
Options inherited from parent commands¶
-c, --config string Path to mvaictl config directory (default "~/.mvaictl")
--warnings-as-errors Treat warnings received from the server as errors and exit with a non-zero exit code
SEE ALSO¶
- mvaictl workload - Operations on workloads