mutli-cluster-ingress-nginx服务不通

[whoisfisher]

mutli-cluster-ingress-nginx服务不通，Pod里面可以使用[svcname].[namespace].svc.clusterset.local:[port]正常访问，但是multi-ingress无法通信，提示504错误。 而且正常的ingress服务也变成404了 这是multi-cluster-ingress ![Uploading image.png…]() 这是普通的ingress ![Uploading image.png…]()

NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):

Kubernetes version (use kubectl version):

Environment:

• Cloud provider or hardware configuration:

• OS (e.g. from /etc/os-release):

• Kernel (e.g. uname -a):

• Install tools:

  • Please mention how/where was the cluster created like kubeadm/kops/minikube/kind etc.

• Basic cluster related info:

  • kubectl version
  • kubectl get nodes -o wide

• How was the ingress-nginx-controller installed:

  • If helm was used then please show output of helm ls -A | grep -i ingress
  • If helm was used then please show output of helm -n <ingresscontrollernamepspace> get values <helmreleasename>
  • If helm was not used, then copy/paste the complete precise command used to install the controller, along with the flags and options used
  • if you have more than one instance of the ingress-nginx-controller installed in the same cluster, please provide details for all the instances

• Current State of the controller:

  • kubectl describe ingressclasses
  • kubectl -n <ingresscontrollernamespace> get all -A -o wide
  • kubectl -n <ingresscontrollernamespace> describe po <ingresscontrollerpodname>
  • kubectl -n <ingresscontrollernamespace> describe svc <ingresscontrollerservicename>

• Current state of ingress object, if applicable:

  • kubectl -n <appnnamespace> get all,ing -o wide
  • kubectl -n <appnamespace> describe ing <ingressname>
  • If applicable, then, your complete and exact curl/grpcurl command (redacted if required) and the reponse to the curl/grpcurl command with the -v flag

• Others:

  • Any other related information like ;
  • copy/paste of the snippet (if applicable)
  • kubectl describe ... of any custom configmap(s) created and in use
  • Any other related information that may help

What happened:

What you expected to happen:

How to reproduce it:

Anything else we need to know:

[XiShanYongYe-Chang]

刚刚有社区小伙伴测试过功能是正常的：https://github.com/karmada-io/multi-cluster-ingress-nginx/pull/14#issuecomment-1593112036

是不是Multi-cluster Ingress文档某个地方写的不清楚导致步骤出错了呢?

而且正常的ingress服务也变成404了

你指的正常的ingress服务是 karmada 控制面上的，还是成员集群中的ingress服务？MCI的功能应该是不会影响但集群Ingress的功能的。

[whoisfisher]

@XiShanYongYe-Chang

就是我在karmada的host集群上部署在同一个应用，然后创建了ingress，可以正常访问,在ingress-controller-manager中启用了karmada相关的参数后，这个ingress不能用了，访问编程404了，但是可以创建multi-cluster-ingress，创建成功后访问提示504

我用的ingress是github中的charts目录下那个

[XiShanYongYe-Chang]

@whoisfisher 我理解你的意思了，对于ingress-controller-manager来说，我把对ingress的支持修改为了mci，所以ingress确实是不能使用了。这个仓库只是一个demo，展示怎么使用mci，如果要使用还需要自己来开发一个ingress controller。