karmada-io / multi-cluster-ingress-nginx Goto Github PK

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

这是普通的ingress

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:

In some scenario, our clusters are uniformly initialized that have overlap clusterIP and serviceIP network segment, so we need to use Globalnet services of Submariner. But these Globalnet services that have EXTERNAL-IP are created by Submariner, like below submariner-etcfrt5unwnek3jrjr4joya6kfly4q6b, so how to auto discovery these services?

[root@member139 ~]# kubectl get services
NAME                                          TYPE        CLUSTER-IP      EXTERNAL-IP     PORT(S)   AGE
kubernetes                                    ClusterIP   10.96.0.1       <none>          443/TCP   20d
serve                                         ClusterIP   10.106.208.67   <none>          80/TCP    5d
submariner-etcfrt5unwnek3jrjr4joya6kfly4q6b   ClusterIP   10.104.94.141   242.1.255.252   80/TCP    5d

I want to directly deploy multi-cluster-ingress-nginx in production env, not to use make dev-env.

Whether can it support official multi-cluster-ingress-nginx image, or using directly ingress-nginx image?