Rename Ark to Velero!!!

Signed-off-by: Nolan Brubaker <brubakern@vmware.com>

.github/ISSUE_TEMPLATE/bug_report.md

@@ -14,11 +14,11 @@ about: Tell us about a problem you are experiencing
 **The output of the following commands will help us better understand what's going on**:
 (Pasting long output into a [GitHub gist](https://gist.github.com) or other pastebin is fine.)
 
-* `kubectl logs deployment/ark -n heptio-ark`
-* `ark backup describe <backupname>` or `kubectl get backup/<backupname> -n heptio-ark -o yaml`
-* `ark backup logs <backupname>`
-* `ark restore describe <restorename>` or `kubectl get restore/<restorename> -n heptio-ark -o yaml`
-* `ark restore logs <restorename>`
+* `kubectl logs deployment/velero -n velero`
+* `velero backup describe <backupname>` or `kubectl get backup/<backupname> -n velero -o yaml`
+* `velero backup logs <backupname>`
+* `velero restore describe <restorename>` or `kubectl get restore/<restorename> -n velero -o yaml`
+* `velero restore logs <restorename>`
 
 
 **Anything else you would like to add:**
@@ -27,7 +27,7 @@ about: Tell us about a problem you are experiencing
 
 **Environment:**
 
-- Ark version (use `ark version`): 
+- Velero version (use `velero version`): 
 - Kubernetes version (use `kubectl version`):
 - Kubernetes installer & version:
 - Cloud provider or hardware configuration:

.github/ISSUE_TEMPLATE/feature-enhancement-request.md

@@ -14,7 +14,7 @@ about: Suggest an idea for this project
 
 **Environment:**
 
-- Ark version (use `ark version`):
+- Velero version (use `velero version`):
 - Kubernetes version (use `kubectl version`):
 - Kubernetes installer & version:
 - Cloud provider or hardware configuration:

.gitignore

@@ -27,7 +27,7 @@ _testmain.go
 
 debug
 
-/ark
+/velero
 .idea/
 
 .container-*

.goreleaser.yml

@@ -17,7 +17,7 @@ before:
   hooks:
     - ./hack/set-example-tags.sh
 builds:
-  - main: ./cmd/ark/main.go
+  - main: ./cmd/velero/main.go
     env:
       - CGO_ENABLED=0
     goos:
@@ -39,7 +39,7 @@ builds:
       - goos: windows
         goarch: arm64
     ldflags:
-      - -X "github.com/heptio/ark/pkg/buildinfo.Version={{ .Tag }}" -X "github.com/heptio/ark/pkg/buildinfo.GitSHA={{ .FullCommit }}" -X "github.com/heptio/ark/pkg/buildinfo.GitTreeState={{ .Env.GIT_TREE_STATE }}"
+      - -X "github.com/heptio/velero/pkg/buildinfo.Version={{ .Tag }}" -X "github.com/heptio/velero/pkg/buildinfo.GitSHA={{ .FullCommit }}" -X "github.com/heptio/velero/pkg/buildinfo.GitTreeState={{ .Env.GIT_TREE_STATE }}"
 archive:
   name_template: "{{ .ProjectName }}-{{ .Tag }}-{{ .Os }}-{{ .Arch }}"
   files:
@@ -50,5 +50,5 @@ checksum:
 release:
   github:
     owner: heptio
-    name: ark
+    name: velero
   draft: true

CODE_OF_CONDUCT.md

@@ -1,4 +1,4 @@
-# Heptio Ark Community Code of Conduct
+# Velero Community Code of Conduct
 
 ## Contributor Code of Conduct
 

CONTRIBUTING.md

@@ -7,7 +7,7 @@ should be a new file created in the `changelogs/unreleased` folder. The file sho
 naming convention of `pr-username` and the contents of the file should be your text for the
 changelog.
 
-    ark/changelogs/unreleased   <- folder
+    velero/changelogs/unreleased   <- folder
         000-username            <- file
 
 

Dockerfile-ark-restic-restore-helper.alpine → Dockerfile-velero-restic-restore-helper.alpine

@@ -16,8 +16,8 @@ FROM alpine:3.8
 
 MAINTAINER Steve Kriss <steve@heptio.com>
 
-ADD /bin/linux/amd64/ark-restic-restore-helper .
+ADD /bin/linux/amd64/velero-restic-restore-helper .
 
 USER nobody:nobody
 
-ENTRYPOINT [ "/ark-restic-restore-helper" ]
+ENTRYPOINT [ "/velero-restic-restore-helper" ]

Dockerfile-ark.alpine → Dockerfile-velero.alpine

@@ -24,8 +24,8 @@ RUN apk add --update --no-cache bzip2 && \
     mv restic_0.9.3_linux_amd64 /usr/bin/restic && \
     chmod +x /usr/bin/restic
 
-ADD /bin/linux/amd64/ark /ark
+ADD /bin/linux/amd64/velero /velero
 
 USER nobody:nobody
 
-ENTRYPOINT ["/ark"]
+ENTRYPOINT ["/velero"]

Makefile

@@ -15,10 +15,10 @@
 # limitations under the License.
 
 # The binary to build (just the basename).
-BIN ?= ark
+BIN ?= velero
 
 # This repo's root import path (under GOPATH).
-PKG := github.com/heptio/ark
+PKG := github.com/heptio/velero
 
 # Where to push the docker image.
 REGISTRY ?= gcr.io/heptio-images
@@ -63,7 +63,7 @@ IMAGE = $(REGISTRY)/$(BIN)
 # If you want to build AND push all containers, see the 'all-push' rule.
 all:
 	@$(MAKE) build
-	@$(MAKE) build BIN=ark-restic-restore-helper
+	@$(MAKE) build BIN=velero-restic-restore-helper
 
 build-%:
 	@$(MAKE) --no-print-directory ARCH=$* build
@@ -104,7 +104,7 @@ _output/bin/$(GOOS)/$(GOARCH)/$(BIN): build-dirs
 
 TTY := $(shell tty -s && echo "-t")
 
-BUILDER_IMAGE := ark-builder
+BUILDER_IMAGE := velero-builder
 
 # Example: make shell CMD="date > datefile"
 shell: build-dirs build-image
@@ -146,7 +146,7 @@ endif
 
 all-containers:
 	$(MAKE) container
-	$(MAKE) container BIN=ark-restic-restore-helper
+	$(MAKE) container BIN=velero-restic-restore-helper
 	$(MAKE) build-fsfreeze
 
 container: verify test .container-$(DOTFILE_IMAGE) container-name
@@ -160,7 +160,7 @@ container-name:
 
 all-push:
 	$(MAKE) push
-	$(MAKE) push BIN=ark-restic-restore-helper
+	$(MAKE) push BIN=velero-restic-restore-helper
 	$(MAKE) push-fsfreeze
 
 

README.md

@@ -1,35 +1,36 @@
-# Heptio Ark
+# Velero
 
-**Maintainers:** [Heptio][0]
+![](velero.png)
 
 [![Build Status][1]][2] <a href="https://zenhub.com"><img src="https://raw.githubusercontent.com/ZenHubIO/support/master/zenhub-badge.png"></a>
 
+## Heptio Ark is now Velero! 
+
+#### We're working on our first Velero release and instructions for migrating your Ark deployments to Velero. Stay tuned!
+
 ## Overview
 
-Ark gives you tools to back up and restore your Kubernetes cluster resources and persistent volumes. Ark lets you:
+Velero gives you tools to back up and restore your Kubernetes cluster resources and persistent volumes. Velero lets you:
 
 * Take backups of your cluster and restore in case of loss.
 * Copy cluster resources to other clusters.
 * Replicate your production environment for development and testing environments.
 
-Ark consists of:
+Velero consists of:
 
 * A server that runs on your cluster
 * A command-line client that runs locally
 
-You can run Ark in clusters on a cloud provider or on-premises. For detailed information, see [Compatible Storage Providers][99].
+You can run Velero in clusters on a cloud provider or on-premises. For detailed information, see [Compatible Storage Providers][99].
 
-## Breaking changes
-
-Ark version 0.10.0 introduces a number of breaking changes. Before you upgrade to version 0.10.0, make sure to read [the documentation on upgrading][98].
 
 ## More information
 
-[The documentation][29] provides a getting started guide, plus information about building from source, architecture, extending Ark, and more.
+[The documentation][29] provides a getting started guide, plus information about building from source, architecture, extending Velero, and more.
 
 ## Troubleshooting
 
-If you encounter issues, review the [troubleshooting docs][30], [file an issue][4], or talk to us on the [#ark-dr channel][25] on the Kubernetes Slack server. 
+If you encounter issues, review the [troubleshooting docs][30], [file an issue][4], or talk to us on the [#velero channel][25] on the Kubernetes Slack server. 
 
 ## Contributing
 
@@ -51,29 +52,26 @@ Feedback and discussion are available on [the mailing list][24].
 
 See [the list of releases][6] to find out about feature changes.
 
-[0]: https://github.com/heptio
-[1]: https://travis-ci.org/heptio/ark.svg?branch=master
-[2]: https://travis-ci.org/heptio/ark
+[1]: https://travis-ci.org/heptio/velero.svg?branch=master
+[2]: https://travis-ci.org/heptio/velero
 
-[4]: https://github.com/heptio/ark/issues
-[5]: https://github.com/heptio/ark/blob/master/CONTRIBUTING.md
-[6]: https://github.com/heptio/ark/releases
+[4]: https://github.com/heptio/velero/issues
+[5]: https://github.com/heptio/velero/blob/master/CONTRIBUTING.md
+[6]: https://github.com/heptio/velero/releases
 
-[8]: https://github.com/heptio/ark/blob/master/CODE_OF_CONDUCT.md
+[8]: https://github.com/heptio/velero/blob/master/CODE_OF_CONDUCT.md
 [9]: https://kubernetes.io/docs/setup/
 [10]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-with-homebrew-on-macos
 [11]: https://kubernetes.io/docs/tasks/tools/install-kubectl/#tabset-1
 [12]: https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/dns/README.md
 [14]: https://github.com/kubernetes/kubernetes
 
-
-[24]: http://j.hept.io/ark-list
-[25]: https://kubernetes.slack.com/messages/ark-dr
-[26]: https://github.com/heptio/ark/blob/master/docs/zenhub.md
+[24]: https://groups.google.com/forum/#!forum/projectvelero
+[25]: https://kubernetes.slack.com/messages/velero
+[26]: https://github.com/heptio/velero/blob/master/docs/zenhub.md
 
 
-[29]: https://heptio.github.io/ark/
+[29]: https://heptio.github.io/velero/
 [30]: /docs/troubleshooting.md
 
-[98]: /docs/upgrading-to-v0.10.md
 [99]: /docs/support-matrix.md

SUPPORT.md

@@ -1,5 +1,5 @@
-# Ark Support
+# Velero Support
 
-Thanks for trying out Ark! We welcome all feedback, please consider joining our mailing list: 
+Thanks for trying out Velero! We welcome all feedback, please consider joining our mailing list: 
 
-- [Mailing List](http://j.hept.io/ark-list)
+- [Mailing List](http://j.hept.io/ark-list)

changelogs/CHANGELOG-0.10.md

@@ -245,5 +245,5 @@ need to be updated for v0.10.
 - 	[eabef085](https://github.com/heptio/ark/commit/eabef085)	Update generated Ark code based on the 1.11 k8s.io/code-generator script
 - 	[f5eac0b4](https://github.com/heptio/ark/commit/f5eac0b4)	Update vendored library code for Kubernetes 1.11
 
-[1]: https://github.com/heptio/ark/blob/master/docs/upgrading-to-v0.10.md
+[1]: https://heptio.github.io/velero/v0.10.0/upgrading-to-v0.10
 [2]: locations.md

changelogs/CHANGELOG-0.8.md

@@ -77,9 +77,9 @@
   here are the steps you can take to upgrade:
 
 1. Execute the steps from the **Credentials and configuration** section for your cloud:
-    * [AWS](https://heptio.github.io/ark/v0.8.0/aws-config#credentials-and-configuration)
-    * [Azure](https://heptio.github.io/ark/v0.8.0/azure-config#credentials-and-configuration)
-    * [GCP](https://heptio.github.io/ark/v0.8.0/gcp-config#credentials-and-configuration)
+    * [AWS](https://heptio.github.io/velero/v0.8.0/aws-config#credentials-and-configuration)
+    * [Azure](https://heptio.github.io/velero/v0.8.0/azure-config#credentials-and-configuration)
+    * [GCP](https://heptio.github.io/velero/v0.8.0/gcp-config#credentials-and-configuration)
 
     When you get to the secret creation step, if you don't have your `credentials-ark` file handy, 
     you can copy the existing secret from your `heptio-ark-server` namespace into the `heptio-ark` namespace:
@@ -95,6 +95,6 @@
     ```
 
 3. Execute the commands from the **Start the server** section for your cloud:
-    * [AWS](https://heptio.github.io/ark/v0.8.0/aws-config#start-the-server)
-    * [Azure](https://heptio.github.io/ark/v0.8.0/azure-config#start-the-server)
-    * [GCP](https://heptio.github.io/ark/v0.8.0/gcp-config#start-the-server)
+    * [AWS](https://heptio.github.io/velero/v0.8.0/aws-config#start-the-server)
+    * [Azure](https://heptio.github.io/velero/v0.8.0/azure-config#start-the-server)
+    * [GCP](https://heptio.github.io/velero/v0.8.0/gcp-config#start-the-server)

changelogs/unreleased/rename-nrb

@@ -0,0 +1 @@
+Renamed Heptio Ark to Velero. Changed internal imports, environment variables, and binary name.

cmd/ark-restic-restore-helper/main.go → cmd/velero-restic-restore-helper/main.go

@@ -45,7 +45,7 @@ func main() {
 }
 
 // done returns true if for each directory under /restores, a file exists
-// within the .ark/ subdirectory whose name is equal to os.Args[1], or
+// within the .velero/ subdirectory whose name is equal to os.Args[1], or
 // false otherwise
 func done() bool {
 	children, err := ioutil.ReadDir("/restores")
@@ -60,7 +60,7 @@ func done() bool {
 			continue
 		}
 
-		doneFile := filepath.Join("/restores", child.Name(), ".ark", os.Args[1])
+		doneFile := filepath.Join("/restores", child.Name(), ".velero", os.Args[1])
 
 		if _, err := os.Stat(doneFile); os.IsNotExist(err) {
 			fmt.Printf("Not found: %s\n", doneFile)

cmd/ark/main.go → cmd/velero/main.go

@@ -22,15 +22,15 @@ import (
 
 	"github.com/golang/glog"
 
-	"github.com/heptio/ark/pkg/cmd"
-	"github.com/heptio/ark/pkg/cmd/ark"
+	"github.com/heptio/velero/pkg/cmd"
+	"github.com/heptio/velero/pkg/cmd/velero"
 )
 
 func main() {
 	defer glog.Flush()
 
 	baseName := filepath.Base(os.Args[0])
 
-	err := ark.NewCommand(baseName).Execute()
+	err := velero.NewCommand(baseName).Execute()
 	cmd.CheckError(err)
 }

docs/about.md

@@ -1,10 +1,10 @@
-# How Ark Works
+# How Velero Works
 
-Each Ark operation -- on-demand backup, scheduled backup, restore -- is a custom resource, defined with a Kubernetes [Custom Resource Definition (CRD)][20] and stored in [etcd][22]. Ark also includes controllers that process the custom resources to perform backups, restores, and all related operations.
+Each Velero operation -- on-demand backup, scheduled backup, restore -- is a custom resource, defined with a Kubernetes [Custom Resource Definition (CRD)][20] and stored in [etcd][22]. Velero also includes controllers that process the custom resources to perform backups, restores, and all related operations.
 
 You can back up or restore all objects in your cluster, or you can filter objects by type, namespace, and/or label.
 
-Ark is ideal for the disaster recovery use case, as well as for snapshotting your application state, prior to performing system operations on your cluster (e.g. upgrades).
+Velero is ideal for the disaster recovery use case, as well as for snapshotting your application state, prior to performing system operations on your cluster (e.g. upgrades).
 
 ## On-demand backups
 
@@ -27,37 +27,37 @@ Scheduled backups are saved with the name `<SCHEDULE NAME>-<TIMESTAMP>`, where `
 
 ## Restores
 
-The **restore** operation allows you to restore all of the objects and persistent volumes from a previously created backup. You can also restore only a filtered subset of objects and persistent volumes. Ark supports multiple namespace remapping--for example, in a single restore, objects in namespace "abc" can be recreated under namespace "def", and the objects in namespace "123" under "456".
+The **restore** operation allows you to restore all of the objects and persistent volumes from a previously created backup. You can also restore only a filtered subset of objects and persistent volumes. Velero supports multiple namespace remapping--for example, in a single restore, objects in namespace "abc" can be recreated under namespace "def", and the objects in namespace "123" under "456".
 
-The default name of a restore is `<BACKUP NAME>-<TIMESTAMP>`, where `<TIMESTAMP>` is formatted as *YYYYMMDDhhmmss*. You can also specify a custom name. A restored object also includes a label with key `ark.heptio.com/restore-name` and value `<RESTORE NAME>`.
+The default name of a restore is `<BACKUP NAME>-<TIMESTAMP>`, where `<TIMESTAMP>` is formatted as *YYYYMMDDhhmmss*. You can also specify a custom name. A restored object also includes a label with key `velero.io/restore-name` and value `<RESTORE NAME>`.
 
-You can also run the Ark server in restore-only mode, which disables backup, schedule, and garbage collection functionality during disaster recovery.
+You can also run the Velero server in restore-only mode, which disables backup, schedule, and garbage collection functionality during disaster recovery.
 
 ## Backup workflow
 
-When you run `ark backup create test-backup`:
+When you run `velero backup create test-backup`:
 
-1. The Ark client makes a call to the Kubernetes API server to create a `Backup` object.
+1. The Velero client makes a call to the Kubernetes API server to create a `Backup` object.
 
 1. The `BackupController` notices the new `Backup` object and performs validation.
 
 1. The `BackupController` begins the backup process. It collects the data to back up by querying the API server for resources.
 
 1. The `BackupController` makes a call to the object storage service -- for example, AWS S3 -- to upload the backup file.
 
-By default, `ark backup create` makes disk snapshots of any persistent volumes. You can adjust the snapshots by specifying additional flags. Run `ark backup create --help` to see available flags. Snapshots can be disabled with the option `--snapshot-volumes=false`.
+By default, `velero backup create` makes disk snapshots of any persistent volumes. You can adjust the snapshots by specifying additional flags. Run `velero backup create --help` to see available flags. Snapshots can be disabled with the option `--snapshot-volumes=false`.
 
 ![19]
 
 ## Backed-up API versions
 
-Ark backs up resources using the Kubernetes API server's *preferred version* for each group/resource. When restoring a resource, this same API group/version must exist in the target cluster in order for the restore to be successful.
+Velero backs up resources using the Kubernetes API server's *preferred version* for each group/resource. When restoring a resource, this same API group/version must exist in the target cluster in order for the restore to be successful.
 
 For example, if the cluster being backed up has a `gizmos` resource in the `things` API group, with group/versions `things/v1alpha1`, `things/v1beta1`, and `things/v1`, and the server's preferred group/version is `things/v1`, then all `gizmos` will be backed up from the `things/v1` API endpoint. When backups from this cluster are restored, the target cluster **must** have the `things/v1` endpoint in order for `gizmos` to be restored. Note that `things/v1` **does not** need to be the preferred version in the target cluster; it just needs to exist.
 
 ## Set a backup to expire
 
-When you create a backup, you can specify a TTL by adding the flag `--ttl <DURATION>`. If Ark sees that an existing backup resource is expired, it removes:
+When you create a backup, you can specify a TTL by adding the flag `--ttl <DURATION>`. If Velero sees that an existing backup resource is expired, it removes:
 
 * The backup resource
 * The backup file from cloud object storage
@@ -66,7 +66,7 @@ When you create a backup, you can specify a TTL by adding the flag `--ttl <DURAT
 
 ## Object storage sync
 
-Heptio Ark treats object storage as the source of truth. It continuously checks to see that the correct backup resources are always present. If there is a properly formatted backup file in the storage bucket, but no corresponding backup resource in the Kubernetes API, Ark synchronizes the information from object storage to Kubernetes.
+Velero treats object storage as the source of truth. It continuously checks to see that the correct backup resources are always present. If there is a properly formatted backup file in the storage bucket, but no corresponding backup resource in the Kubernetes API, Velero synchronizes the information from object storage to Kubernetes.
 
 This allows restore functionality to work in a cluster migration scenario, where the original backup objects do not exist in the new cluster.
 

docs/api-types/README.md

@@ -2,7 +2,7 @@
 
 ## API types
 
-Here we list the API types that have some functionality that you can only configure via json/yaml vs the `ark` cli
+Here we list the API types that have some functionality that you can only configure via json/yaml vs the `velero` cli
 (hooks)
 
 * [Backup][1]