You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2021/05/08 02:29:32 UTC
[GitHub] [apisix-ingress-controller] WinSuperStar opened a new issue #426: request help: apisix-ingress-controller run in kubeSphere,It doesn't work！
WinSuperStar opened a new issue #426:
URL: https://github.com/apache/apisix-ingress-controller/issues/426
### Issue description
When I try to test the connection on KubeSphere following the practice example:
https://apisix.apache.org/docs/ingress-controller/practices/proxy-the-httpbin-service-with-ingress
-------httpbin-apisix-ingress.yaml begin-----
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
name: httpbin-apisix-ingress
namespace: dev-httpbin
# Note for ingress.networking.k8s.io/v1beta1,
# you have to carry annotation kubernetes.io/ingress.class,
# and its value must be matched with the one configured in
# apisix-ingress-controller, in our case, it's apisix.
annotations:
kubernetes.io/ingress.class: apisix
spec:
rules:
- host: local.httpbin.org
http:
paths:
- backend:
serviceName: httpbin
servicePort: 80
path: /
pathType: Prefix
-------httpbin-apisix-ingress.yaml end-----
---------------error log begin --------------------------
2021-05-07T22:29:45+08:00 error controller/endpoint.go:141 failed to get upstream {"upstream": "dev-httpbin_httpbin_80", "cluster": "name=; base_url=http://apisix-admin:9180/apisix/admin", "error": "Get http://apisix-admin:9180/apisix/admin/upstreams/d18cbca1: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"}
2021-05-07T22:29:45+08:00 warn controller/endpoint.go:169 sync endpoints failed, will retry {"object": {"Type":1,"Object":{"metadata":{"name":"httpbin","namespace":"dev-httpbin","selfLink":"/api/v1/namespaces/dev-httpbin/endpoints/httpbin","uid":"dc35b312-9b08-4f2b-ad02-328d89169441","resourceVersion":"7126710","creationTimestamp":"2021-05-06T05:43:56Z","labels":{"run":"httpbin"},"annotations":{"endpoints.kubernetes.io/last-change-trigger-time":"2021-05-06T05:46:29Z"},"managedFields":[{"manager":"kube-controller-manager","operation":"Update","apiVersion":"v1","time":"2021-05-06T05:46:29Z","fieldsType":"FieldsV1","fieldsV1":{"f:metadata":{"f:annotations":{".":{},"f:endpoints.kubernetes.io/last-change-trigger-time":{}},"f:labels":{".":{},"f:run":{}}},"f:subsets":{}}}]},"subsets":[{"addresses":[{"ip":"172.16.23.186","nodeName":"dev-k8s-node2","targetRef":{"kind":"Pod","namespace":"dev-httpbin","name":"httpbin","uid":"afb0308a-99d4-40ff-a2aa-1da24250ef87","resource
Version":"7126708"}}],"ports":[{"port":80,"protocol":"TCP"}]}]},"Tombstone":null}}
---------------error log end--------------------------
and also i got the warn message like this :
---------------warn message begin --------------
[GIN] 2021/05/08 - 10:28:05 | 200 | 34.264µs | 10.41.17.19 | GET "/healthz"
2021-05-08T10:28:05+08:00 warn controller/endpoint.go:93 service kube-system/kube-scheduler was deleted
2021-05-08T10:28:06+08:00 warn controller/endpoint.go:93 service default/ceph.com-cephfs was deleted
2021-05-08T10:28:07+08:00 warn controller/endpoint.go:93 service default/ceph.com-rbd was deleted
2021-05-08T10:28:07+08:00 warn controller/endpoint.go:93 service kube-system/kube-controller-manager was deleted
2021-05-08T10:28:07+08:00 warn controller/endpoint.go:93 service kube-system/kube-scheduler was deleted
2021-05-08T10:28:08+08:00 warn controller/endpoint.go:93 service default/ceph.com-cephfs was deleted
2021-05-08T10:28:09+08:00 warn controller/endpoint.go:93 service default/ceph.com-rbd was deleted
2021-05-08T10:28:09+08:00 warn controller/endpoint.go:93 service kube-system/kube-controller-manager was deleted
2021-05-08T10:28:09+08:00 warn controller/endpoint.go:93 service kube-system/kube-scheduler was deleted
2021-05-08T10:28:10+08:00 warn controller/endpoint.go:93 service default/ceph.com-cephfs was deleted
[GIN] 2021/05/08 - 10:28:10 | 200 | 31.724µs | 10.41.17.19 | GET "/healthz"
2021-05-08T10:28:11+08:00 warn controller/endpoint.go:93 service default/ceph.com-rbd was deleted
2021-05-08T10:28:11+08:00 warn controller/endpoint.go:93 service kube-system/kube-controller-manager was deleted
2021-05-08T10:28:11+08:00 warn controller/endpoint.go:93 service kube-system/kube-scheduler was deleted
2021-05-08T10:28:12+08:00 warn controller/endpoint.go:93 service default/ceph.com-cephfs was deleted
2021-05-08T10:28:13+08:00 warn controller/endpoint.go:93 service default/ceph.com-rbd was deleted
2021-05-08T10:28:13+08:00 warn controller/endpoint.go:93 service kube-system/kube-controller-manager was deleted
2021-05-08T10:28:13+08:00 warn controller/endpoint.go:93 service kube-system/kube-scheduler was deleted
---------------warn message end--------------
### Environment
* your apisix-ingress-controller version (output of `apisix-ingress-controller version --long`); 0.5.0
* your Kubernetes cluster version (output of `kubectl version`); Kubernetes 1.18.2 and kubeSphere 3.0
* if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (`uname -a`).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #426: request help: apisix-ingress-controller run in kubeSphere,It doesn't work！
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #426:
URL: https://github.com/apache/apisix-ingress-controller/issues/426#issuecomment-835165671
@WinSuperStar How did you deploy apisix-ingress-controller, what's the configuration about command line option `--ingress-version`?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] WinSuperStar commented on issue #426: request help: apisix-ingress-controller run in kubeSphere,It doesn't work！
Posted by GitBox <gi...@apache.org>.
WinSuperStar commented on issue #426:
URL: https://github.com/apache/apisix-ingress-controller/issues/426#issuecomment-835183712
@tokers
You remind me that I cloned the source code to the local installation before. There may be some problems. I just uninstalled it and then re installed the apisix-ingress-controller. I see that It’s all right now. Thank you very much!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers closed issue #426: request help: apisix-ingress-controller run in kubeSphere,It doesn't work！
Posted by GitBox <gi...@apache.org>.
tokers closed issue #426:
URL: https://github.com/apache/apisix-ingress-controller/issues/426
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #426: request help: apisix-ingress-controller run in kubeSphere,It doesn't work！
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #426:
URL: https://github.com/apache/apisix-ingress-controller/issues/426#issuecomment-835189944
@WinSuperStar Feel free to ask any questions here!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org