lookup minio.velero.svc on : no such host

[rxy0210]

What steps did you take and what happened:

When I do describe backup, tell me "dial tcp: lookup minio.velero.svc on 8.8.8:53: no such host"

What did you expect to happen:
no warning and error

The following information will help us better understand what's going on:
I deployed the environment according to this document.https://velero.io/docs/v1.9/contributions/minio/#accessing-logs-with-an-https-endpoint

[root@ velero]# kubectl -nvelero get po
NAME                      READY   STATUS      RESTARTS   AGE
minio-f957674b9-lsqs5     1/1     Running     0          81m
minio-setup-9zzm2         0/1     Completed   0          81m
velero-65d8b9984d-7btfk   1/1     Running     0          32m

But when I performed this step, I got this prompt.

[root@ velero]# velero backup describe nginx-backup
Name:         nginx-backup
Namespace:    velero
Labels:       velero.io/storage-location=default
Annotations:  velero.io/resource-timeout=10m0s
              velero.io/source-cluster-k8s-gitversion=v1.21.5
              velero.io/source-cluster-k8s-major-version=1
              velero.io/source-cluster-k8s-minor-version=21+

Phase:  PartiallyFailed (run `velero backup logs nginx-backup` for more information)

Warnings:  <error getting warnings: Get "http://minio.velero.svc:9000/velero/backups/nginx-backup/nginx-backup-results.gz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=minio%2F20250122%2Fminio%2Fs3%2Faws4_request&X-Amz-Date=20250122T020612Z&X-Amz-Expires=600&X-Amz-SignedHeaders=host&X-Amz-Signature=71e752da4224d1e1577e91f449157c0731722dbd5c2fe3e1b42d158495fd4108": dial tcp: lookup minio.velero.svc on 8.8.8.8:53: no such host>

Errors:  <error getting errors: Get "http://minio.velero.svc:9000/velero/backups/nginx-backup/nginx-backup-results.gz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=minio%2F20250122%2Fminio%2Fs3%2Faws4_request&X-Amz-Date=20250122T020612Z&X-Amz-Expires=600&X-Amz-SignedHeaders=host&X-Amz-Signature=71e752da4224d1e1577e91f449157c0731722dbd5c2fe3e1b42d158495fd4108": dial tcp: lookup minio.velero.svc on 8.8.8.8:53: no such host>

Namespaces:
  Included:  *
  Excluded:  <none>

Resources:
  Included:        *
  Excluded:        <none>
  Cluster-scoped:  auto

Label selector:  app=nginx

Or label selector:  <none>

Storage Location:  default

Velero-Native Snapshot PVs:  auto
Snapshot Move Data:          false
Data Mover:                  velero

TTL:  720h0m0s

CSISnapshotTimeout:    10m0s
ItemOperationTimeout:  4h0m0s

Hooks:  <none>

Backup Format Version:  1.1.0

Started:    2025-01-22 10:06:02 +0800 CST
Completed:  2025-01-22 10:06:07 +0800 CST

Expiration:  2025-02-21 10:06:02 +0800 CST

Total items to be backed up:  32
Items backed up:              32

Backup Volumes:
  <error getting backup volume info: Get "http://minio.velero.svc:9000/velero/backups/nginx-backup/nginx-backup-volumeinfo.json.gz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=minio%2F20250122%2Fminio%2Fs3%2Faws4_request&X-Amz-Date=20250122T020612Z&X-Amz-Expires=600&X-Amz-SignedHeaders=host&X-Amz-Signature=88aa01b0f6612b635d405b9fe362ae4790d8d34113bb885f53f711bbb71a06be": dial tcp: lookup minio.velero.svc on 8.8.8.8:53: no such host>

HooksAttempted:  0
HooksFailed:     0

Why is that?

Is that the problem here?

[root@ velero]# kubectl -nvelero exec -it  minio-f957674b9-lsqs5 -- mc alias ls
mc: Configuration written to `/tmp/.mc/config.json`. Please update your access credentials.
mc: Successfully created `/tmp/.mc/share`.
mc: Initialized share uploads `/tmp/.mc/share/uploads.json` file.
mc: Initialized share downloads `/tmp/.mc/share/downloads.json` file.
gcs
  URL       : https://storage.googleapis.com
  AccessKey : YOUR-ACCESS-KEY-HERE
  SecretKey : YOUR-SECRET-KEY-HERE
  API       : S3v2
  Path      : dns
  Src       : /tmp/.mc/config.json

local
  URL       : http://localhost:9000
  AccessKey :
  SecretKey :
  API       :
  Path      : auto
  Src       : /tmp/.mc/config.json

play
  URL       : https://play.min.io
  AccessKey : Q3AM3UQ867SPQQA43P2F
  SecretKey : zuf+tfteSlswRu7BJ86wekitnifILbZam1KYY3TG
  API       : S3v4
  Path      : auto
  Src       : /tmp/.mc/config.json

s3
  URL       : https://s3.amazonaws.com
  AccessKey : YOUR-ACCESS-KEY-HERE
  SecretKey : YOUR-SECRET-KEY-HERE
  API       : S3v4
  Path      : dns
  Src       : /tmp/.mc/config.json

Anything else you would like to add:

Environment:

• Velero version (use velero version): v1.15.0
• Velero features (use velero client config get features): features:
• Kubernetes version (use kubectl version):"v1.21.5
• Kubernetes installer & version:"v1.21.5
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

• 👍 for "I would like to see this bug fixed as soon as possible"
• 👎 for "There are more important bugs to focus on right now"

[Lyndon-Li]

Looks like an object store connection problem, check if minio.velero.svc:9000 is accessible from pods.