mirrors/velero
1
0
Fork 0
mirror of https://github.com/vmware-tanzu/velero.git synced 2026-01-07 13:55:20 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #2321 from skriss/fix-install-docs

Browse Source 
update docs for installing with kubectl apply
This commit is contained in:
Nolan Brubaker
2020-03-05 17:11:16 -05:00
committed by GitHub
parent cc848fb3b9 b11086a3d4
commit bdb9145375
2 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
site/docs/master/customize-installation.md
View File

@@ -92,7 +92,7 @@ To generate the YAML without applying it to your cluster, use the `--dry-run -o
This is useful for applying bespoke customizations, integrating with a GitOps workflow, etc.
If you are installing Velero in Kubernetes 1.13.x or earlier, you need to use `kubectl apply`'s `--validate=false` option when applying the generated configuration to your cluster. See [issue 2077][7] for more context.
If you are installing Velero in Kubernetes 1.14.x or earlier, you need to use `kubectl apply`'s `--validate=false` option when applying the generated configuration to your cluster. See [issue 2077][7] and [issue 2311][8] for more context.
## Additional options
@@ -244,3 +244,4 @@ If you get an error like `complete:13: command not found: compdef`, then add the
[4]: on-premises.md
[6]: velero-install.md#usage
[7]: https://github.com/vmware-tanzu/velero/issues/2077
[8]: https://github.com/vmware-tanzu/velero/issues/2311

3
site/docs/v1.3.0/customize-installation.md
View File

@@ -92,7 +92,7 @@ To generate the YAML without applying it to your cluster, use the `--dry-run -o
This is useful for applying bespoke customizations, integrating with a GitOps workflow, etc.
If you are installing Velero in Kubernetes 1.13.x or earlier, you need to use `kubectl apply`'s `--validate=false` option when applying the generated configuration to your cluster. See [issue 2077][7] for more context.
If you are installing Velero in Kubernetes 1.14.x or earlier, you need to use `kubectl apply`'s `--validate=false` option when applying the generated configuration to your cluster. See [issue 2077][7] and [issue 2311][8] for more context.
## Additional options
@@ -244,3 +244,4 @@ If you get an error like `complete:13: command not found: compdef`, then add the
[4]: on-premises.md
[6]: velero-install.md#usage
[7]: https://github.com/vmware-tanzu/velero/issues/2077
[8]: https://github.com/vmware-tanzu/velero/issues/2311