创建部署问题时,请参考下面模板,你提供的信息越多,越容易及时获得解答。如果未按模板创建问题,管理员有权关闭问题。
确保帖子格式清晰易读,用 markdown code block 语法格式化代码块。
你只花一分钟创建的问题,不能指望别人花上半个小时给你解答。

操作系统信

Ubuntu 22.0.4, 8C 16G

Kubernetes版本信息
kubectl version 命令执行结果贴在下方

WARNING: This version information is deprecated and will be replaced with the output from kubectl version –short. Use –output=yaml|json to get the full version.

Client Version: version.Info{Major:“1”, Minor:“26”, GitVersion:“v1.26.15”, GitCommit:“1649f592f1909b97aa3c2a0a8f968a3fd05a7b8b”, GitTreeState:“clean”, BuildDate:“2024-03-14T01:05:39Z”, GoVersion:“go1.21.8”, Compiler:“gc”, Platform:“linux/amd64”}

Kustomize Version: v4.5.7

Server Version: version.Info{Major:“1”, Minor:“26”, GitVersion:“v1.26.15”, GitCommit:“1649f592f1909b97aa3c2a0a8f968a3fd05a7b8b”, GitTreeState:“clean”, BuildDate:“2024-03-14T00:54:27Z”, GoVersion:“go1.21.8”, Compiler:“gc”, Platform:“linux/amd64”}

容器运行时
docker version / crictl version / nerdctl version 结果贴在下方

Version: 0.1.0

RuntimeName: containerd

RuntimeVersion: v1.7.13

RuntimeApiVersion: v1

KubeSphere版本信息
例如:v2.1.1/v3.0.0。离线安装还是在线安装。在已有K8s上安装还是使用kk安装。

kk安装,3.4.1

问题是什么
在Kubesphere上部署了服务,采用Ingress方式提供域名访问,发现域名访问不了,CoreDNS已经配置

# Please edit the object below. Lines beginning with a ‘#’ will be ignored,

# and an empty file will abort the edit. If an error occurs while saving this file will be

# reopened with the relevant failures.

#

apiVersion: v1

data:

Corefile: |

.:53 {

    errors

    health {

      lameduck 5s

    }

    ready

    kubernetes cluster.local in-addr.arpa ip6.arpa {

      pods insecure

      fallthrough in-addr.arpa ip6.arpa

      ttl 30

    }

    hosts {

      10\.167.96.84  k8s-master.cluster.local k8s-master

      10\.167.96.85  k8s-node1.cluster.local k8s-node1

      10\.167.96.86  k8s-node2.cluster.local k8s-node2

      10\.167.96.87  k8s-node3.cluster.local k8s-node3

      10\.167.96.88  k8s-node4.cluster.local k8s-node4

      10\.167.96.84  lb.kubesphere.local

      10\.167.96.84 kdp-ux.kdp-e2e.io

      10\.167.96.84 grafana.kdp-e2e.io

      10\.167.96.84 prometheus.kdp-e2e.io

      10\.167.96.84 alertmanager.kdp-e2e.io

      10\.167.96.84 cloudtty.kdp-e2e.io

      10\.167.96.84 flink-session-cluster-kdp-data.kdp-e2e.io

      10\.167.96.84 hdfs-namenode-0-kdp-data.kdp-e2e.io

      10\.167.96.84 hdfs-namenode-1-kdp-data.kdp-e2e.ioairbyte-kdp-data.kdp-e2e.io

      10\.167.96.84 hue-kdp-data.kdp-e2e.io

      10\.167.96.84 kafka-manager-kdp-data.kdp-e2e.io

      10\.167.96.84 minio-kdp-data-api.kdp-e2e.io

      10\.167.96.84 spark-history-server-kdp-data.kdp-e2e.io

      10\.167.96.84 streampark-kdp-data.kdp-e2e.io

      10\.167.96.84 airbyte-kdp-data.kdp-e2e.io

      fallthrough

    }

    prometheus :9153

    forward . /etc/resolv.conf {

      prefer_udp

      max_concurrent 1000

    }