vmware-tanzu
/
velero
mirror of https://github.com/vmware-tanzu/velero.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

document --validate=false flag for manual installation to v1.13/earlier (#2172) 

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

Co-authored-by: Ashish Amarnath <ashish.amarnath@gmail.com>
pull/2177/head
Steve Kriss 2020-01-06 15:34:05 -07:00 committed by Carlisia Campos
parent 408c0dfb5a
commit f43c1ad55e
2 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -83,13 +83,16 @@ 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. 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.
## Additional options ## Additional options
Run `velero install --help` or see the [Helm chart documentation](https://github.com/helm/charts/tree/master/stable/velero) for the full set of installation options. Run `velero install --help` or see the [Helm chart documentation](https://github.com/helm/charts/tree/master/stable/velero) for the full set of installation options.
[0]: supported-providers.md
[1]: https://github.com/vmware-tanzu/velero/releases/latest [1]: https://github.com/vmware-tanzu/velero/releases/latest
[2]: namespace.md [2]: namespace.md
[3]: restic.md [3]: restic.md
[4]: on-premises.md [4]: on-premises.md
[6]: velero-install.md#usage [6]: velero-install.md#usage
[7]: https://github.com/vmware-tanzu/velero/issues/2077

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

@ -83,6 +83,8 @@ 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. 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.
## Additional options ## Additional options
Run `velero install --help` or see the [Helm chart documentation](https://github.com/helm/charts/tree/master/stable/velero) for the full set of installation options. Run `velero install --help` or see the [Helm chart documentation](https://github.com/helm/charts/tree/master/stable/velero) for the full set of installation options.
@ -93,3 +95,4 @@ Run `velero install --help` or see the [Helm chart documentation](https://github
[3]: restic.md [3]: restic.md
[4]: on-premises.md [4]: on-premises.md
[6]: velero-install.md#usage [6]: velero-install.md#usage
[7]: https://github.com/vmware-tanzu/velero/issues/2077