-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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.
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
no such host error #7763
Comments
Is your Minio service accessible from the host you performing CLI From backup description you provide, are you backing up the whole cluster? BTW, no logs of backup |
| Is your Minio service accessible from the host you performing CLI velero describe, you can check it using CLI mc? | From backup description you provide, are you backing up the whole cluster?
|
What's the output of |
Upon commands |
If its a DNS issue then how its performing k8s-cluster-backup and you can see in MINIO GUI screen shot. Not sure its intermediate issue or not? Both backup I took using yaml as below not using velero CLI.
|
The The backup and restore create command creates a backup or restore CR by calling the client-go library, and then the Velero controller gets the CR creation event. The backup and restore is performed in the k8s cluster, and the backup and restore result is uploaded to the MinIO. The |
If you're in a situation where the BSL is not available at the same DNS address locally as in the cluster, you may need to run the Velero CLI from a pod in the cluster. |
Error I got when I run cli from outside of the cluster. Another question is why schedule backup not happening? |
K8s version 1.29
Velero version 1.13.0 using helm
CMD
kubectl get all -n minio-store
kubectl get schedule -n velero
velero get backup
-CMD
velero describe backup test-20240501061604
The text was updated successfully, but these errors were encountered: