Skip to content

Commit

Permalink
Add note about EKS permission issue (#97)
Browse files Browse the repository at this point in the history
  • Loading branch information
a-mccarthy authored Jan 5, 2022
1 parent 7f0a121 commit dea5d98
Showing 1 changed file with 7 additions and 2 deletions.
9 changes: 7 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -284,6 +284,13 @@ velero install \
Additionally, you can specify `--use-restic` to enable restic support, and `--wait` to wait for the deployment to be ready.
**Note:** If you are using EKS, there is a [known permissions issue](https://github.com/vmware-tanzu/velero/issues/3138) when using Velero with Kubernetes versions 1.18 and earlier that will prevent the Velero from being able to read S3 storage locations. To fix this, update the Velero deployment yaml file to include following `securityContext` value:
```
securityContext:
fsGroup: 65534
```
(Optional) Specify [additional configurable parameters][7] for the `--backup-location-config` flag.
(Optional) Specify [additional configurable parameters][8] for the `--snapshot-location-config` flag.
Expand Down Expand Up @@ -388,5 +395,3 @@ Copy one of the returned IDs `<ID>` and use it with the `aws` CLI tool to search
[101]: https://github.com/vmware-tanzu/velero-plugin-for-aws/workflows/Main%20CI/badge.svg
[102]: https://github.com/vmware-tanzu/velero-plugin-for-aws/actions?query=workflow%3A"Main+CI"
[103]: https://github.com/vmware-tanzu/velero/issues/new/choose


0 comments on commit dea5d98

Please sign in to comment.