Add doc changes for 0.7.0 #313

Bradamant3 · 2018-02-14T18:06:09Z

Fixes #290

skriss

Initial set of comments, still reviewing

skriss · 2018-02-14T18:20:08Z

README.md


-* **Cross-cloud-provider migration** for Kubernetes API objects (cross-cloud-provider migration of persistent volume snapshots not yet supported)
+* Manage disaster recovery.
+* Copy cluster resources across cloud providers. NOTE: PersistenVolume objects are not supported.


PersistenVolume -> PersistentVolume

Not sure what the best wording is but we should clarify that cloud volume migrations are not supported. Technically, PV objects (i.e. the k8s objects are)

skriss · 2018-02-14T18:22:15Z

README.md

-> NOTE: Documentation may change between releases. See the [Changelog][20] for links to previous versions of this repository and its docs.
->
-> To ensure that you are working off a specific release, `git checkout <VERSION_TAG>` where `<VERSION_TAG>` is the appropriate tag for the Ark version you wish to use (e.g. "v0.3.3"). You should `git checkout master` only if you're planning on [building the Ark image from scratch][7].
+NOTE: Make sure to check out the appropriate version. TODO: fix up this text


skriss · 2018-02-14T18:24:59Z

README.md


-* **Cross-cloud-provider migration** for Kubernetes API objects (cross-cloud-provider migration of persistent volume snapshots not yet supported)
+* Manage disaster recovery.


I find this kinda fuzzy, maybe something like "take periodic backups of your cluster and restore in case of loss" (i.e. highlight that this is the in-place backup/recovery use case)?

skriss · 2018-02-14T18:26:48Z

README.md

-* **Cross-cloud-provider migration** for Kubernetes API objects (cross-cloud-provider migration of persistent volume snapshots not yet supported)
+* Manage disaster recovery.
+* Copy cluster resources across cloud providers. NOTE: PersistenVolume objects are not supported.
+* Replicate your production environment for dev and testing enviornments.


enviornments -> environments

skriss · 2018-02-14T18:27:18Z

README.md

-1. *Configurable subsets of Kubernetes API objects* -- as tarballs stored in object storage
-2. *Disk snapshots of Persistent Volumes* -- via the cloud provider APIs
+* A server that runs on your cluster
+* A client with a CLI


"client with a CLI" seems redundant

skriss · 2018-02-14T18:30:49Z

README.md

-NAME                          BACKUP         STATUS      WARNINGS   ERRORS    CREATED                         SELECTOR
-nginx-backup-20170727200524   nginx-backup   Completed   0          0         2017-07-27 20:05:24 +0000 UTC   <none>
-```
+1. Create a backup for any object that matches the `app=nginx` label selector:


Maybe we should switch this to backup the namespace? Effect is the same, just maybe clearer. @ncdc @nrb thoughts?

SGTM but not required for v0.7.0

I don't think it's a bad change, but I also agree that probably not as important for v0.7.0.

In this vein, it may be useful to provide a couple different examples in the docs later - using labels, using a namespace, excluding resources.

skriss · 2018-02-14T18:31:46Z

README.md


-1. The *ark client* makes a call to the Kubernetes API server, creating a `Backup` custom resource (which is stored in [etcd][22]).
+    Your output should look like the following:


This may take a couple seconds to complete; do we want a note that it might show as InProgress at first?

skriss · 2018-02-14T18:32:02Z

README.md


-## Extensibility
+For more information, see [the debugging information][18].


broken link

skriss · 2018-02-14T18:32:17Z

README.md


- To learn more about Heptio Ark operations and their applications, see the [`/docs` directory][3].
+[The documentation] provides detailed information about building from source, architecture, extending Ark, and more.


broken link

Correct link is now added, but it will be broken until we merge the gh-pages branch to upstream

skriss · 2018-02-14T18:32:54Z

docs/about.md

+Ark provides the following operations:
+
+* Backups
+* Schedules


Scheduled Backups?

skriss · 2018-02-14T18:36:39Z

README.md

@@ -5,167 +5,142 @@
 [![Build Status][1]][2]


On the sidebar, I don't see an explicit link to get back to README.md once you've navigated away (only clicking on the upper-left Heptio Ark gets there). Should/could we have a "Quickstart" link at the top of the nav to make this more obvious/easy

I know :-(
I've attempted several solutions to this problem, unsuccessfully so far. I'll keep playing.

Attempt #N: wdyt?

skriss · 2018-02-14T18:37:30Z

docs/about.md

+
+Each operation is a custom resource, defined with a Kubernetes [Custom Resource Definition (CRD)][20] and stored in [etcd][22]. An additional custom resource, Config, specifies cloud provider settings. These resources are handled by [custom controllers][21] when their corresponding requests are submitted to the Kubernetes API server.
+
+Each controller watches its custom resource for API requests (Ark operations), performs validation, and handles most of the logic for interacting with the cloud provider API -- for example, managing object storage and persistent volumes.


most of the logic makes me wonder as a reader what it doesn't handle/why that's not explained

Ditto - let's remove the ambiguity. We handle all of it :)

skriss · 2018-02-14T18:39:08Z

docs/about.md

+
+### Restores
+
+The *restore* operation allows you to restore all of the objects and persistent volumes from a previously created Backup. Heptio Ark supports multiple namespace remapping--for example, in a single restore, objects in namespace "abc" can be recreated under namespace "def", and the ones in "123" under "456".


maybe objects backed up from namespace "abc"?

skriss · 2018-02-14T18:43:15Z

docs/cloud-common.md

+```bash
+kubectl delete namespaces nginx-example
+```
+


wait for NS to be deleted?

skriss · 2018-02-14T18:44:24Z

docs/cloud-common.md

+
+```bash
+kubectl delete namespaces nginx-example
+kubectl delete pv $nginx_pv_name


I don't think this step to delete PVs is necessary (should be done automatically, although maybe there was a bug in the Azure provisioner?) but in any case this references a variable that we're not setting so won't work as-is.

skriss · 2018-02-14T18:45:50Z

docs/cloud-common.md

+ark restore create nginx-backup
+```
+
+## Expired backup deletion


This section and the following seem out of place on this page

ncdc

Please make sure the .DS_Store files don't get added :)

ncdc · 2018-02-14T18:22:41Z

docs/about.md

+
+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).
+
+Ark consists of a server and a client.


Remove this line?

ncdc · 2018-02-14T18:22:55Z

docs/about.md

+
+Ark consists of a server and a client.
+
+## Server


Call this "Features"?

ncdc · 2018-02-14T18:23:07Z

docs/about.md

+
+Ark provides the following operations:
+
+* Backups


One-time backups? Ad-hoc backups?

ncdc · 2018-02-14T18:23:13Z

docs/about.md

+Ark provides the following operations:
+
+* Backups
+* Schedules


Scheduled backups?

ncdc · 2018-02-14T18:24:41Z

docs/about.md

+
+Each operation is a custom resource, defined with a Kubernetes [Custom Resource Definition (CRD)][20] and stored in [etcd][22]. An additional custom resource, Config, specifies cloud provider settings. These resources are handled by [custom controllers][21] when their corresponding requests are submitted to the Kubernetes API server.
+
+Each controller watches its custom resource for API requests (Ark operations), performs validation, and handles most of the logic for interacting with the cloud provider API -- for example, managing object storage and persistent volumes.


validations

ncdc · 2018-02-14T18:50:50Z

docs/gcp-config.md

+You can run Kubernetes on Google Cloud Platform in either of: 
+
+* Kubernetes on Google Compute Engine virtual machines
+* With Google Kubernetes Engine 


Remove "With"?

ncdc · 2018-02-14T18:51:31Z

docs/gcp-config.md

+If you run Google Kubernetes Engine (GKE), make sure that your current IAM user is a cluster-admin. This role is required to create RBAC objects.
+See [the GKE documentation][22] for more information.
+
+In the Ark root directory, run the following to first set up namespaces, RBAC, and other scaffolding. To run in a custom namespace, make sure that you have edited the YAML file to specify the namespace. See [Run in custom namespace][0].


ncdc · 2018-02-14T18:51:39Z

docs/gcp-config.md

+
+```bash
+kubectl create secret generic cloud-credentials \
+    --namespace heptio-ark \


Adjust if needed

ncdc · 2018-02-14T18:51:52Z

docs/gcp-config.md

+
+* (Optional) If you run the nginx example, in file `examples/nginx-app/with-pv.yaml`:
+
+    * Replace `<YOUR_STORAGE_CLASS_NAME>` with `standard`. This is GCP's default `StorageClass` name.


Same comment as above re storageclass

ncdc · 2018-02-14T18:52:02Z

docs/gcp-config.md

+
+  ```bash
+  kubectl apply -f examples/common/10-deployment.yaml
+  kubectl apply -f examples/gcp/00-ark-config.yaml


Do config first

skriss · 2018-02-14T19:03:53Z

For the sidebar nav, I think the following is the best order (@ncdc @nrb feel free to object):

Intro
Cloud Provider
Tutorials
Customize
Troubleshooting

ncdc · 2018-02-14T19:05:22Z

Probably not for today/tomorrow, but I feel like after Intro, we need Installation

Bradamant3 · 2018-02-14T20:01:28Z

Is Installation basically what's under Cloud Provider atm? Trivial to change title in nav bar and corresponding topic titles, although a bit more content would probably also be needed ...
Also wrt Tutorials -- I'd rather not move them up the tree until they're better fleshed out as tutorials. But that's next on the list.

ncdc · 2018-02-14T20:48:44Z

Yeah, I'd say so.

Bradamant3 · 2018-02-14T22:07:54Z

Just pushed interim changes; not all fixes are in yet. Still TODO: gcp.md, remove stray unwanted files

Bradamant3 · 2018-02-15T04:06:21Z

Almost there; final cleanup in the morning.

Bradamant3 · 2018-02-15T14:24:51Z

@ncdc fixes you requested should all be in now, along with a bunch of other stuff smallish and larger. Mostly fixed up links, added one file for better IA in built docs (extend.md)

ncdc · 2018-02-15T14:37:59Z

docs/build-from-scratch.md


 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.

-Set the `$REGISTRY` environment variable (used in the `Makefile`) if you want to push the Heptio Ark images to your own registry. This allows any node in your cluster to pull your locally built image.
+Set the `$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.

 `$PROJECT` and `$VERSION` environment variables are also specified in the `Makefile`, and can be similarly modified as desired.


$PROJECT is not currently valid any more. We hard code the image name to ark but you can customize the image's tag by changing $VERSION. We can revisit the customizability later, if needed.

ncdc · 2018-02-15T14:38:55Z

docs/build-from-scratch.md

-All binaries are placed in `_output/bin/<GOOS>/<GOARCH>`, e.g. `_output/bin/darwin/amd64/ark`.
+By default, `make` builds an `ark` binary that runs on your host operating system and architecture. 
+To build for another platform, run `make build-<GOOS>-<GOARCH`.
+For example, to build for the Mac, you runo `make build-darwin-amd64`.


ncdc · 2018-02-15T14:40:51Z

README.md


-* **Cross-cloud-provider migration** for Kubernetes API objects (cross-cloud-provider migration of persistent volume snapshots not yet supported)
+* Take backups of your cluster and restore in case of loss.
+* Copy cluster resources across cloud providers. NOTE: Cloud volume migrations are not supported.


Mind saying "not yet"?

ncdc · 2018-02-15T14:42:52Z

README.md


-Note that this example *does not* include a demonstration of PV disk snapshots, because that feature requires integration with a cloud provider API. For snapshotting examples and instructions specific to AWS, GCP, and Azure, see [Cloud Provider Specifics][23].
+* Access to a Kubernetes cluster, version 1.7 or later


FYI, you need at least 1.7.5 for ark backup delete to work

ncdc · 2018-02-15T14:43:56Z

README.md

-> NOTE: Documentation may change between releases. See the [Changelog][20] for links to previous versions of this repository and its docs.
->
-> To ensure that you are working off a specific release, `git checkout <VERSION_TAG>` where `<VERSION_TAG>` is the appropriate tag for the Ark version you wish to use (e.g. "v0.3.3"). You should `git checkout master` only if you're planning on [building the Ark image from scratch][7].
+NOTE: Make sure to check out the appropriate version.


Is it worth expanding just a little bit here, suggesting they check out the latest git tag, and commenting that master is under active development and things may be in flux?

ncdc · 2018-02-15T14:44:59Z

README.md

-## Architecture
+    ```
+    kubectl get deployments --namespace=nginx-example
+    kubectl get services --namespace=nginx-example


Also kubectl get namespace/nginx-example

ncdc · 2018-02-15T14:45:38Z

README.md


-4. Once the data has been aggregated, the `BackupController` makes a call to the object storage service (e.g. Amazon S3) to upload the backup file.
+After a successful restore, the `STATUS` column is `Completed`, and `WARNINGS` and `ERRORS` are 0. All objects in the `nginx-example` should be just as they were before you deleted them.


All objects in the nginx-example namespace ...

ncdc · 2018-02-15T14:46:01Z

README.md


-## Extensibility
+```
+ark restore get <RESTORE_NAME> -o yaml


This needs to be ark restore describe <RESTORE_NAME>

ncdc · 2018-02-15T14:47:57Z

docs/about.md

+
+Note that cluster backups are not strictly atomic. If Kubernetes objects are being created or edited at the time of backup, they might not be included in the backup. The odds of capturing inconsistent information are low, but it is possible.
+
+On-demand backups are saved with the `<BACKUP NAME>` specified during creation.


I'm not entirely sure what this is saying?

ncdc · 2018-02-15T14:49:52Z

docs/about.md

+
+Here's what happens when you run `ark backup create test-backup`:
+
+1. The Ark client makes a call to the Kubernetes API server to create a `Backup` object from the custom resource.


Please strike from the custom resource. We could mention that it includes all the parameters you specified on the command line - namespaces to include/exclude, resources to include/exclude, label selector.

ncdc · 2018-02-15T14:51:58Z

docs/build-from-scratch.md


-## 0. Prerequisites
+* Access to a Kubernetes cluster, version 1.7 or later


Same comment re 1.7.5+ for backup deletions to work

ncdc · 2018-02-15T14:53:20Z

docs/cli-reference/README.md


 ## Running the client

-While it is possible to build and run the `ark` executable yourself, it is recommended to use the containerized version. Use the alias described in the quickstart:
+While it is possible to build and run the `ark` executable yourself, we recommend that you run the containerized version. 


Please remove all text related to running the containerized version of the client. We only recommend they download a pre-built release, or if they desire, one they built from source.

ncdc · 2018-02-15T16:14:27Z

README.md


 If there are errors or warnings, you can look at them in detail:

 ```
-ark restore get <RESTORE_NAME> -o yaml
+ark restore describe <RESTORE_NAME> -o yaml


Please remove -o yaml

nrb

Thanks for this @Bradamant3! Most of my comments are about clarity rather than content.

Also it looks like the .DS_Store file is included; it should probably be omitted.

nrb · 2018-02-15T16:20:36Z

README.md

-* **Cross-cloud-provider migration** for Kubernetes API objects (cross-cloud-provider migration of persistent volume snapshots not yet supported)
+* Take backups of your cluster and restore in case of loss.
+* Copy cluster resources across cloud providers. NOTE: Cloud volume migrations are not yet supported.
+* Replicate your production environment for dev and testing environments.


I would probably spell out 'development' here.

nrb · 2018-02-15T16:22:17Z

README.md

-1. *Configurable subsets of Kubernetes API objects* -- as tarballs stored in object storage
-2. *Disk snapshots of Persistent Volumes* -- via the cloud provider APIs
+* A server that runs on your cluster
+* A CLI


Perhaps "A command line client that runs on a local computer?" The server part mentions where it runs, but the line for the CLI could be a bit ambiguous for some.

nrb · 2018-02-15T16:23:30Z

README.md


-Note that this example *does not* include a demonstration of PV disk snapshots, because that feature requires integration with a cloud provider API. For snapshotting examples and instructions specific to AWS, GCP, and Azure, see [Cloud Provider Specifics][23].
+* Access to a Kubernetes cluster, version 1.7 or later. Version 1.7.5 is required to run `ark backup delete`.


Should it be "Version 1.7.5 or higher is required to run ark backup delete."? I assume it doesn't work on exclusively 1.7.5.

nrb · 2018-02-15T16:25:32Z

README.md

-NAME                          BACKUP         STATUS      WARNINGS   ERRORS    CREATED                         SELECTOR
-nginx-backup-20170727200524   nginx-backup   Completed   0          0         2017-07-27 20:05:24 +0000 UTC   <none>
-```
+1. Create a backup for any object that matches the `app=nginx` label selector:


I don't think it's a bad change, but I also agree that probably not as important for v0.7.0.

In this vein, it may be useful to provide a couple different examples in the docs later - using labels, using a namespace, excluding resources.

nrb · 2018-02-15T16:27:16Z

README.md


-Ark has multiple mechanisms for extending the core functionality to meet your individual backup/restore needs:
+For more information, see [the debugging information][18].


"Information" is repeated twice in the same sentence - maybe "see the debugging section" for the link text? Or "For more details, see the debugging information"

nrb · 2018-02-15T16:30:02Z

docs/about.md

+* Scheduled backups
+* Restores
+
+Each operation is a custom resource, defined with a Kubernetes [Custom Resource Definition (CRD)][20] and stored in [etcd][22]. An additional custom resource, Config, specifies cloud provider settings. These resources are handled by [custom controllers][21] when their corresponding requests are submitted to the Kubernetes API server.


I don't think Config is solely about cloud provider settings, though those are certainly included. Maybe something like "An additional custom resource, Config, specifies required information and customization options, such as cloud provider settings".

I'm fine if we leave this as-is, or if we make changes. Not a huge deal, especially once we get to backup targets.

nrb · 2018-02-15T16:32:00Z

docs/about.md

+
+1. Uploads a tarball of copied Kubernetes objects into cloud object storage.
+
+1. Calls the cloud provider API to make disk snapshots of persistent volumes, if specified.


I think it's been mentioned elsewhere, but things like Minio and Rook aren't necessarily cloud providers, though Ark could operate against them. Maybe refer to 'block storage API' instead of 'cloud provider' here.

Let's hold off changing any language here until we do backup targets. This is fine for now.

nrb · 2018-02-15T16:34:04Z

docs/about.md

+* All PersistentVolume snapshots
+* All associated Restores
+
+## Cloud storage sync


Similar to above about cloud providers, maybe "Object storage sync"?

No need to change this now

nrb · 2018-02-15T16:37:19Z

docs/build-from-scratch.md


-## 0. Prerequisites
+* Access to a Kubernetes cluster, version 1.7 or later. Version 1.7.5 is required to run `ark backup delete`.


Same comment from elsewhere - "1.7.5 or higher", in case someone jumps straight to this doc.

ncdc · 2018-02-15T18:04:20Z

docs/about.md


-Each controller watches its custom resource for API requests (Ark operations), performs validations, and handles the logic for interacting with the cloud provider API -- for example, managing object storage and persistent volumes.
+Each controller watches its custom resource for API requests (Ark operations), performs validations, and handles the logic for interacting with the block storage API -- for example, managing object storage and persistent volumes.


Please undo this change - keep it as cloud provider API

ncdc · 2018-02-15T18:04:27Z

docs/about.md


 ### On-demand backups

 The **backup** operation:

 1. Uploads a tarball of copied Kubernetes objects into cloud object storage.

-1. Calls the cloud provider API to make disk snapshots of persistent volumes, if specified.
+1. Calls the block storage API to make disk snapshots of persistent volumes, if specified.


ncdc · 2018-02-15T18:05:00Z

docs/about.md

@@ -70,11 +70,11 @@ When you create a backup, you can specify a TTL by adding the flag `--ttl <DURAT
 * All PersistentVolume snapshots
 * All associated Restores

-## Cloud storage sync
+## Object storage sync


This change is probably ok

Signed-off-by: JENNIFER RONDEAU <jrondeau@heptio.com>

* OADP-3654: fix CVE CVE-2024-24786 * update go.sum

Bradamant3 force-pushed the 0.7-doc-updates branch from 9354171 to 9704de8 Compare February 14, 2018 18:06

skriss reviewed Feb 14, 2018

View reviewed changes

ncdc suggested changes Feb 14, 2018

View reviewed changes

Bradamant3 force-pushed the 0.7-doc-updates branch 2 times, most recently from 18d9f4c to 007ed05 Compare February 15, 2018 04:03

ncdc reviewed Feb 15, 2018

View reviewed changes

Bradamant3 force-pushed the 0.7-doc-updates branch from 0639982 to 00a48e1 Compare February 15, 2018 16:22

nrb reviewed Feb 15, 2018

View reviewed changes

ncdc approved these changes Feb 15, 2018

View reviewed changes

ncdc reviewed Feb 15, 2018

View reviewed changes

Bradamant3 force-pushed the 0.7-doc-updates branch from 3f6fb09 to 7d646a8 Compare February 15, 2018 18:16

ncdc changed the title ~~[wip] [do-not-merge] add doc changes for 0.7.0~~ Add doc changes for 0.7.0 Feb 15, 2018

add doc changes for 0.7.0

3b8e32f

Signed-off-by: JENNIFER RONDEAU <jrondeau@heptio.com>

Bradamant3 force-pushed the 0.7-doc-updates branch from 7d646a8 to 3b8e32f Compare February 15, 2018 18:27

ncdc closed this Feb 15, 2018

ncdc reopened this Feb 15, 2018

ncdc closed this Feb 15, 2018

ncdc reopened this Feb 15, 2018

ncdc merged commit f449e23 into vmware-tanzu:master Feb 15, 2018

Bradamant3 deleted the 0.7-doc-updates branch November 8, 2018 13:05

kaovilai pushed a commit to kaovilai/velero that referenced this pull request Jun 11, 2024

[oadp-1.3] OADP-3654: fix CVE CVE-2024-24786 (vmware-tanzu#313)

8c40468

* OADP-3654: fix CVE CVE-2024-24786 * update go.sum


		* Cross-cloud-provider migration for Kubernetes API objects (cross-cloud-provider migration of persistent volume snapshots not yet supported)
		* Manage disaster recovery.


		1. The ark client makes a call to the Kubernetes API server, creating a `Backup` custom resource (which is stored in [etcd][22]).
		Your output should look like the following:


		## Extensibility
		For more information, see [the debugging information][18].


		To learn more about Heptio Ark operations and their applications, see the [`/docs` directory][3].
		[The documentation] provides detailed information about building from source, architecture, extending Ark, and more.


		Each operation is a custom resource, defined with a Kubernetes [Custom Resource Definition (CRD)][20] and stored in [etcd][22]. An additional custom resource, Config, specifies cloud provider settings. These resources are handled by [custom controllers][21] when their corresponding requests are submitted to the Kubernetes API server.

		Each controller watches its custom resource for API requests (Ark operations), performs validation, and handles most of the logic for interacting with the cloud provider API -- for example, managing object storage and persistent volumes.


		### Restores

		The restore operation allows you to restore all of the objects and persistent volumes from a previously created Backup. Heptio Ark supports multiple namespace remapping--for example, in a single restore, objects in namespace "abc" can be recreated under namespace "def", and the ones in "123" under "456".


		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).

		Ark consists of a server and a client.


		* (Optional) If you run the nginx example, in file `examples/nginx-app/with-pv.yaml`:

		* Replace `<YOUR_STORAGE_CLASS_NAME>` with `standard`. This is GCP's default `StorageClass` name.


		Note that this example does not include a demonstration of PV disk snapshots, because that feature requires integration with a cloud provider API. For snapshotting examples and instructions specific to AWS, GCP, and Azure, see [Cloud Provider Specifics][23].
		* Access to a Kubernetes cluster, version 1.7 or later


		4. Once the data has been aggregated, the `BackupController` makes a call to the object storage service (e.g. Amazon S3) to upload the backup file.
		After a successful restore, the `STATUS` column is `Completed`, and `WARNINGS` and `ERRORS` are 0. All objects in the `nginx-example` should be just as they were before you deleted them.


		Note that cluster backups are not strictly atomic. If Kubernetes objects are being created or edited at the time of backup, they might not be included in the backup. The odds of capturing inconsistent information are low, but it is possible.

		On-demand backups are saved with the `<BACKUP NAME>` specified during creation.


		Here's what happens when you run `ark backup create test-backup`:

		1. The Ark client makes a call to the Kubernetes API server to create a `Backup` object from the custom resource.


		## 0. Prerequisites
		* Access to a Kubernetes cluster, version 1.7 or later


		Ark has multiple mechanisms for extending the core functionality to meet your individual backup/restore needs:
		For more information, see [the debugging information][18].


		1. Uploads a tarball of copied Kubernetes objects into cloud object storage.

		1. Calls the cloud provider API to make disk snapshots of persistent volumes, if specified.

Add doc changes for 0.7.0 #313

Add doc changes for 0.7.0 #313

Conversation

Bradamant3 commented Feb 14, 2018 • edited by ncdc Loading

skriss left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ncdc left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

skriss commented Feb 14, 2018

ncdc commented Feb 14, 2018

Bradamant3 commented Feb 14, 2018

ncdc commented Feb 14, 2018

Bradamant3 commented Feb 14, 2018

Bradamant3 commented Feb 15, 2018

Bradamant3 commented Feb 15, 2018

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

nrb left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Bradamant3 commented Feb 14, 2018 •

edited by ncdc

Loading