replace v1.1.0-beta.1 docs with v1.1.0-beta.2 docs

Signed-off-by: Steve Kriss <krisss@vmware.com>

site/_config.yml

@@ -56,10 +56,10 @@ defaults:
       gh: https://github.com/heptio/velero/tree/master
       layout: "docs"
   - scope:
-      path: docs/v1.1.0-beta.1
+      path: docs/v1.1.0-beta.2
     values:
-      version: v1.1.0-beta.1
-      gh: https://github.com/heptio/velero/tree/v1.1.0-beta.1
+      version: v1.1.0-beta.2
+      gh: https://github.com/heptio/velero/tree/v1.1.0-beta.2
       layout: "docs"
   - scope:
       path: docs/v1.0.0
@@ -148,7 +148,7 @@ versioning: true
 latest: v1.0.0
 versions:
 - master
-- v1.1.0-beta.1
+- v1.1.0-beta.2
 - v1.0.0
 - v0.11.0
 - v0.10.0

site/_data/toc-mapping.yml

@@ -3,7 +3,7 @@
 # that the navigation for older versions still work.
 
 master: master-toc
-v1.1.0-beta.1: v1-1-0-beta-1-toc
+v1.1.0-beta.2: v1-1-0-beta-2-toc
 v1.0.0: v1-0-0-toc
 v0.11.0: v011-toc
 v0.10.0: v010-toc

site/_data/v1-1-0-beta-1-toc.yml → site/_data/v1-1-0-beta-2-toc.yml

@@ -13,6 +13,8 @@ toc:
     subfolderitems:
       - page: Overview
         url: /install-overview
+      - page: Upgrade to 1.1
+        url: /upgrade-to-1.1
       - page: Quick start with in-cluster MinIO
         url: /get-started
       - page: Run on AWS

site/docs/v1.1.0-beta.1/README.md → site/docs/v1.1.0-beta.2/README.md

@@ -58,10 +58,10 @@ See [the list of releases][6] to find out about feature changes.
 [2]: https://travis-ci.org/heptio/velero
 
 [4]: https://github.com/heptio/velero/issues
-[5]: https://github.com/heptio/velero/blob/v1.1.0-beta.1/CONTRIBUTING.md
+[5]: https://github.com/heptio/velero/blob/v1.1.0-beta.2/CONTRIBUTING.md
 [6]: https://github.com/heptio/velero/releases
 
-[8]: https://github.com/heptio/velero/blob/v1.1.0-beta.1/CODE_OF_CONDUCT.md
+[8]: https://github.com/heptio/velero/blob/v1.1.0-beta.2/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
@@ -74,7 +74,7 @@ See [the list of releases][6] to find out about feature changes.
 
 
 [28]: install-overview.md
-[29]: https://velero.io/docs/v1.1.0-beta.1/
+[29]: https://velero.io/docs/v1.1.0-beta.2/
 [30]: troubleshooting.md
 
 [99]: support-matrix.md

site/docs/v1.1.0-beta.1/build-from-source.md → site/docs/v1.1.0-beta.2/build-from-source.md

@@ -238,7 +238,7 @@ If you need to add or update the vendored dependencies, see [Vendoring dependenc
 [10]: #vendoring-dependencies
 [11]: vendoring-dependencies.md
 [12]: #test
-[13]: https://github.com/heptio/velero/blob/v1.1.0-beta.1/hack/generate-proto.sh
+[13]: https://github.com/heptio/velero/blob/v1.1.0-beta.2/hack/generate-proto.sh
 [14]: https://grpc.io/docs/quickstart/go.html#install-protocol-buffers-v3
 [15]: https://docs.aws.amazon.com/cli/latest/topic/config-vars.html#the-shared-credentials-file
 [16]: https://cloud.google.com/docs/authentication/getting-started#setting_the_environment_variable

site/docs/v1.1.0-beta.1/faq.md → site/docs/v1.1.0-beta.2/faq.md

@@ -22,7 +22,7 @@ Examples of cases where Velero is useful:
 
 Yes, with some exceptions. For example, when Velero restores pods it deletes the `nodeName` from the
 pod so that it can be scheduled onto a new node. You can see some more examples of the differences
-in [pod_action.go](https://github.com/heptio/velero/blob/v1.1.0-beta.1/pkg/restore/pod_action.go)
+in [pod_action.go](https://github.com/heptio/velero/blob/v1.1.0-beta.2/pkg/restore/pod_action.go)
 
 ## I'm using Velero in multiple clusters. Should I use the same bucket to store all of my backups?
 

site/docs/v1.1.0-beta.1/hooks.md → site/docs/v1.1.0-beta.2/hooks.md

@@ -77,5 +77,5 @@ velero backup logs nginx-hook-test | grep hookCommand
 
 
 [1]: api-types/backup.md
-[2]: https://github.com/heptio/velero/blob/v1.1.0-beta.1/examples/nginx-app/with-pv.yaml
+[2]: https://github.com/heptio/velero/blob/v1.1.0-beta.2/examples/nginx-app/with-pv.yaml
 [3]: cloud-common.md

site/docs/v1.1.0-beta.1/oracle-config.md → site/docs/v1.1.0-beta.2/oracle-config.md

@@ -241,5 +241,5 @@ After creating the Velero server in your cluster, try this example:
 
 ## Additional Reading 
 
-* [Official Velero Documentation](https://velero.io/docs/v1.1.0-beta.1/)
+* [Official Velero Documentation](https://velero.io/docs/v1.1.0-beta.2/)
 * [Oracle Cloud Infrastructure Documentation](https://docs.cloud.oracle.com/)

site/docs/v1.1.0-beta.1/plugins.md → site/docs/v1.1.0-beta.2/plugins.md

@@ -78,5 +78,5 @@ for an example of this -- in particular, the `getPluginConfig(...)` function.
 
 
 [1]: https://github.com/heptio/velero-plugin-example
-[2]: https://github.com/heptio/velero/blob/v1.1.0-beta.1/pkg/plugin/logger.go
-[3]: https://github.com/heptio/velero/blob/v1.1.0-beta.1/pkg/restore/restic_restore_action.go
+[2]: https://github.com/heptio/velero/blob/v1.1.0-beta.2/pkg/plugin/logger.go
+[3]: https://github.com/heptio/velero/blob/v1.1.0-beta.2/pkg/restore/restic_restore_action.go

site/docs/v1.1.0-beta.1/restic.md → site/docs/v1.1.0-beta.2/restic.md

@@ -235,19 +235,19 @@ data:
   image: myregistry.io/my-custom-helper-image[:OPTIONAL_TAG]
 
   # "cpuRequest" sets the request.cpu value on the restic init containers during restore.
-  # If not set, it will default to "100m".
+  # If not set, it will default to "100m". A value of "0" is treated as unbounded.
   cpuRequest: 200m
   
   # "memRequest" sets the request.memory value on the restic init containers during restore.
-  # If not set, it will default to "128Mi".
+  # If not set, it will default to "128Mi". A value of "0" is treated as unbounded.
   memRequest: 128Mi
 
   # "cpuLimit" sets the request.cpu value on the restic init containers during restore.
-  # If not set, it will default to "100m".
+  # If not set, it will default to "100m". A value of "0" is treated as unbounded.
   cpuLimit: 200m
   
   # "memLimit" sets the request.memory value on the restic init containers during restore.
-  # If not set, it will default to "128Mi".
+  # If not set, it will default to "128Mi". A value of "0" is treated as unbounded.
   memLimit: 128Mi
 
 

site/docs/v1.1.0-beta.2/upgrade-to-1.1.md

@@ -0,0 +1,25 @@
+# Upgrading to Velero 1.1
+
+## Prerequisites
+- [Velero v1.0][1] installed.
+
+Velero v1.1 only requires user intervention if Velero is running in a namespace other than `velero`.
+
+## Instructions
+
+### Adding VELERO_NAMESPACE environment variable to the deployment
+
+Previous versions of Velero's server detected the namespace in which it was running by inspecting the container's filesystem.
+With v1.1, this is no longer the case, and the server must be made aware of the namespace it is running in with the `VELERO_NAMESPACE` environment variable.
+
+`velero install` automatically writes this for new deployments, but existing installations will need to add the environment variable before upgrading.
+
+You can use the following command to patch the deployment:
+
+```bash
+kubectl patch deployment/velero -n <YOUR_NAMESPACE> \
+--type='json' \
+-p='[{"op":"add","path":"/spec/template/spec/containers/0/env/0","value":{"name":"VELERO_NAMESPACE", "valueFrom":{"fieldRef":{"fieldPath":"metadata.namespace"}}}}]'
+```
+
+[1]: https://github.com/heptio/velero/releases/tag/v1.0.0