-
Notifications
You must be signed in to change notification settings - Fork 499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question]: Why does my IngressController experiment not work? #1215
Comments
As a final addendum, cp01 is one of the control planes in the K8S cluster, and again I accessed it from a machine external to the K8S cluster, and of course I added a route to this machine pointing to the CLUSTER IP 10.99.196.179 of service easegress-public. But the result is no response, hang on! traceroute command is also not responding (I'm using the TCP protocol and the destination port in order to be caught by the Iptables rule)
|
Can you post the whole logs of the Easegress ingress controller pod, maybe the reason lies in there? |
ok, logs of Easegress ingress cm pod as follow:
|
Please don't set these two fields, and restart the deployment, then post the log. Because you're doing |
ok, I left the kubeConfig and masterURL values unset and restarted the deployment easegress ConfigMap as follow:
Then I tested it from CP01, which is one of the K8S control planes, and it still didn't work!
I'm also checking the logs in the pod in easegress as follows
The path / here should be responsive, not 404, because the services corresponding to the backend are normal.
I kind of wonder if the httpserver configuration in the example is missing path option
|
|
But I've confirmed that ConfigMap
|
It was created. We just support get/describe traffic gates for different namespaces[1], which will be in next release. But for now, you can use And I was reckoning that your manual installation is not completed. You could use helm[2] to install Ingress Controller with specifying [1] #1197 |
Thanks, I've been on vacation since the Lunar New Year is coming up and I can't access the server, I'll try again after fixing my vacation. |
Sure, please give us feedback if it's still not working. |
I just returned to work yesterday and have been very busy at work and haven't had a chance to look into it yet, give me a moment..... |
Sure, please give us feedback if you have any issues. |
I'm sorry, I've been so busy lately that I haven't had the time to study the methods you've provided, I'll definitely test them out as soon as I'm free after a while! |
@kursk-ye Hi, we've released v2.7.2 to address a bug in Ingress Controller, please upgrade Easegress and check it out. |
ok,I try it |
Thank you very much, it worked! I used the 2.7.2 source code, rebuilt the image for arm64 architecture, and after redeploying easegress and service, the experiment worked!
|
Thanks to the help of the easegress team, I wrote a wechat article about the experimental procedure |
This is not Bug report or Feature request
Is this question answered in the documentation?
Is there an existing issue for this?
Your question
According to this IngressController documentation, I practiced the whole deployment process, but could not access it successfully, each configuration is as follows
ClusterRole, ServiceAccount, ClusterRoleBinding needed for easegress have also been released!
The ingress ingress-example has been successfully released with its ingressClassName set to easegress
service easegress-public has been successfully released with the following configuration
The deployment of easegress corresponding to service easegress-public has also been released and is running, as follow
Here are a few points of clarification:
the mirror privatehub:5000/arm_easegress:2.7.0 used here is compiled by myself on the arm64 architecture, which I have already used in other practices, and I guarantee that there will be no problems!
The ConfigMap easegress-cm used by Deployment has also been released as follows
The content of kubeConfig is taken from the .kube/config file needed to access K8S, and the value of masterURL - "https://172.26.11.55:6443" is the K8S API URL.
I know that according to the documentation Kubernetes Ingress Controller these two values are set when easegress is deployed outside of the K8S cluster, but I also tried not setting these two values, but the result is still not accessible, the result is the same!
The service hello-service and deployment hello-deployment corresponding to the backend are also successfully published and running.
I bypassed ingress and tested that the service and deployment can be accessed successfully.
The ip and port displayed are the respone of my own nginx service definition.
It doesn't feel like there's a problem anywhere, but when I access the NodePort port of the service easegress-public that ingress corresponds to it hangs and fails to respond
The text was updated successfully, but these errors were encountered: