[Bug]新版的ingress不能直接使用 about kubecube HOT 10 CLOSED

[root@zpfrltgup4tujpi1-0001 ~]# kubectl get ingress -n wordpress-space
NAME   CLASS   HOSTS        ADDRESS   PORTS   AGE
ng-1   nginx   a.usudo.cn             80      10h
[root@zpfrltgup4tujpi1-0001 ~]# kubectl get ns
NAME                              STATUS   AGE
default                           Active   18h
elasticsearch                     Active   18h
hnc-system                        Active   18h
ingress-nginx                     Active   18h
kube-node-lease                   Active   18h
kube-public                       Active   18h
kube-system                       Active   18h
kubecube-monitoring               Active   18h
kubecube-project-wordpress        Active   17h
kubecube-system                   Active   18h
kubecube-tenant-wordpresstenant   Active   17h
local-path-storage                Active   18h
wordpress-space                   Active   17h
[root@zpfrltgup4tujpi1-0001 ~]# kubectl get pod -n ingress-nginx
NAME                                        READY   STATUS      RESTARTS   AGE
ingress-nginx-admission-create-cf6mw        0/1     Completed   0          18h
ingress-nginx-admission-patch-6m5kt         0/1     Completed   1          18h
ingress-nginx-controller-776d88d5c9-vptdm   1/1     Running     0          18h
[root@zpfrltgup4tujpi1-0001 ~]# kubectl get service -n ingress-nginx
NAME                                 TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
ingress-nginx-controller             LoadBalancer   10.101.198.84   <pending>     80:30621/TCP,443:32469/TCP   18h
ingress-nginx-controller-admission   ClusterIP      10.98.28.60     <none>        443/TCP                      18h
[root@zpfrltgup4tujpi1-0001 ~]# kubectl logs -n ingress-nginx ingress-nginx-controller-776d88d5c9-vptdm

I0524 14:58:21.313531       8 admission.go:149] processed ingress via admission controller {testedIngressLength:3 testedIngressTime:0.048s renderingIngressLength:3 renderingIngressTime:0s admissionTime:26.4kBs testedConfigurationSize:0.048}
I0524 14:58:21.313570       8 main.go:100] "successfully validated configuration, accepting" ingress="wordpress-space/ng-1"
I0524 14:58:21.316134       8 store.go:474] "creating ingress" ingress="wordpress-space/ng-1" ingressclass="nginx"
I0524 14:58:21.316712       8 event.go:285] Event(v1.ObjectReference{Kind:"Ingress", Namespace:"wordpress-space", Name:"ng-1", UID:"17be4121-7f80-4b25-85ee-54fddec1b4fa", APIVersion:"networking.k8s.io/v1", ResourceVersion:"115139", FieldPath:""}): type: 'Normal' reason: 'Sync' Scheduled for sync
W0524 14:58:21.318857       8 controller.go:1110] Service "kubecube-monitoring/kubecube-monitoring-alertmanager" does not have any active Endpoint.
I0524 14:58:21.318970       8 controller.go:166] "Configuration changes detected, backend reload required"
I0524 14:58:21.410338       8 controller.go:183] "Backend successfully reloaded"
I0524 14:58:21.410989       8 event.go:285] Event(v1.ObjectReference{Kind:"Pod", Namespace:"ingress-nginx", Name:"ingress-nginx-controller-776d88d5c9-vptdm", UID:"cd0e9b8a-4cfb-449e-af78-6fe970d7435a", APIVersion:"v1", ResourceVersion:"1032", FieldPath:""}): type: 'Normal' reason: 'RELOAD' NGINX reload triggered due to a change in configuration