Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The s3 storage target for the same cluster could not be resolved and connected #6372

Closed
clcc2019 opened this issue Jun 8, 2023 · 3 comments
Closed

The s3 storage target for the same cluster could not be resolved and connected #6372

clcc2019 opened this issue Jun 8, 2023 · 3 comments
Assignees
@Lyndon-Li
Labels
1.13-candidate issue/pr that should be considered to target v1.13 minor release

Comments

@clcc2019
Copy link

clcc2019 commented Jun 8, 2023

image

The s3 storage target for the same cluster could not be resolved and connected

velero install \
  --provider aws \
  --bucket tmp \
  --secret-file ./credentials-velero \
  --use-volume-snapshots=true \
  --backup-location-config region=minio,s3ForcePathStyle="true",s3Url="http://10.96.0.205:9000"
@Lyndon-Li
Copy link
Contributor

This is a known issue.
Velero client is connecting to the backup store directly to get items backed up or persisted together with the backup. If the env where Velero client is running has no network connection to the backup store, some client command will fail, i.e., velero backup logs, velero backup download, velero debug

@Lyndon-Li Lyndon-Li self-assigned this Jun 12, 2023
@pradeepkchaturvedi pradeepkchaturvedi added the 1.13-candidate issue/pr that should be considered to target v1.13 minor release label Aug 4, 2023
@Lyndon-Li
Copy link
Contributor

This is duplicated with #6167

@Lyndon-Li
Copy link
Contributor

Close for duplication

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Lyndon-Li Lyndon-Li

Labels
1.13-candidate issue/pr that should be considered to target v1.13 minor release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@clcc2019 @pradeepkchaturvedi @Lyndon-Li