Documentation for version v0.7.1 is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date documentation, see the latest version.
ark backup delete.
Install with go:
go get github.com/heptio/ark
The files are installed in
You can build your Ark image locally on the machine where you run your cluster, or you can push it to a private registry. This section covers both workflows.
$REGISTRY environment variable (used in the
Makefile) to push the Heptio Ark images to your own registry. This allows any node in your cluster to pull your locally built image.
In the Ark root directory, to build your container with the tag
To push your image to a registry, use
The following files are automatically generated from the source code:
If you make any of the following changes, you must run
make update to regenerate
If you make the following change, you must run generate-proto.sh to regenerate files:
make builds an
ark binary that runs on your host operating system and architecture.
To build for another platform, run
For example, to build for the Mac, run
All binaries are placed in
_output/bin/<GOOS>/<GOARCH>– for example,
Makefile has a convenience target,
all-build, that builds the following platforms:
To run unit tests, use
make test. You can also run
make verify to ensure that all generated
files (clientset, listers, shared informers, docs) are up to date.
When running Heptio Ark, you will need to account for the following (all of which are handled in the
See Cloud Provider Specifics for more details.
When your Ark deployment is up and running, you must replace the Heptio-provided Ark image with the image that you built. Run:
kubectl set image deployment/ark ark=$REGISTRY/ark:$VERSION
$VERSION are the values that you built with.
If you need to add or update the vendored dependencies, see Vendoring dependencies.