Skip to content

zarf tools wait-for

zarf tools wait-for

Waits for a given Kubernetes resource to be ready

Synopsis

By default Zarf will wait for all Kubernetes resources to be ready before completion of a component during a deployment. This command can be used to wait for a Kubernetes resources to exist and be ready that may be created by a Gitops tool or a Kubernetes operator. You can also wait for arbitrary network endpoints using REST or TCP checks.

zarf tools wait-for COMMAND [flags]

Examples

# Wait for Kubernetes resources:
$ zarf tools wait-for resource pod my-pod-name ready -n default
$ zarf tools wait-for resource deployment podinfo -n podinfo
$ zarf tools wait-for resource svc zarf-docker-registry exists -n zarf
# Wait for network endpoints:
$ zarf tools wait-for network http localhost:8080 200
$ zarf tools wait-for network tcp localhost:8080

Options

-h, --help help for wait-for

Options inherited from parent commands

-a, --architecture string Architecture for OCI images and Zarf packages
--cache string Specify the location of the Zarf cache directory (default "~/.zarf-cache")
--features stringToString Provide a comma-separated list of feature names to bools to enable or disable. Ex. --features "foo=true,bar=false,baz=true" (default [])
--insecure-skip-tls-verify Skip checking server's certificate for validity. This flag should only be used if you have a specific reason and accept the reduced security posture.
--log-format string Select a logging format. Defaults to 'console'. Valid options are: 'console', 'json', 'dev'. (default "console")
-l, --log-level string Log level when running Zarf. Valid options are: error, warn, info, debug (default "info")
--no-color Disable terminal color codes in logging and stdout prints.
--plain-http Allow OCI registry connections over HTTP instead of HTTPS. This flag should only be used if you have a specific reason and accept the reduced security posture.
--tmpdir string Specify the temporary directory to use for intermediate files

SEE ALSO