[Question]: When using Easegress images version V2.6.1 and above, the IngressController does not function properly. about easegress HOT 5 CLOSED

Hi, resources you have seen is our new feature, it may not cause the problem. I check the release note. During 2.6.1 to 2.6.2, only this pr releated to ingress controller #1089.
@xxx7xxxx could you please recheck this pr to see if there are any potential problems?

By the way, in easegress 2.7.1, we support check resources created by ingress-controller. Please check this part of doc https://github.com/easegress-io/easegress/blob/main/docs/02.Tutorials/2.1.egctl-Usage.md#viewing-and-finding-resources
By using the new command, we may find and fix the problem more quickly.

from easegress.

Ingress controller creates pipelines and httpservers using k8s settings.

use

egctl get pipeline --all-namespaces           
egctl get httpserver --all-namespaces           

to get all resources and then describe it use egctl describe httpserver yyyy --namespace xxxx to check detail yaml.

from easegress.

@tjqc0512 Please post the log of the easegress-ingress-controller. We might get the evidence that causes the error.

from easegress.

@tjqc0512 Hi, we've released v2.7.2 to address a bug in Ingress Controller, please upgrade Easegress and check it out.

from easegress.

@xxx7xxxx
Thank you very much. After using version 2.7.2, it has returned to normal. Adding easegress.ingress.kubernetes.io/proxy-timeout: "20" to the header of the ingress resource configuration file can also solve the problem.

from easegress.