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/11/18 03:56:28 UTC

[GitHub] [apisix-ingress-controller] GhangZh opened a new issue #758: request help:

GhangZh opened a new issue #758:
URL: https://github.com/apache/apisix-ingress-controller/issues/758


   ### Issue description
   apisix-ingress-controller has many reported errors,And there is no manual creation of resources via dashboard. 
   ![image](https://user-images.githubusercontent.com/92301646/142347990-3ffd3596-05e5-4af8-af34-32e0d67683ed.png)
   ![image](https://user-images.githubusercontent.com/92301646/142348006-0f1d3ec1-907a-4dd3-b3e4-6654c473abca.png)
   ![image](https://user-images.githubusercontent.com/92301646/142348011-05b87ee1-bd4c-4a74-823c-1b42c81b2977.png)
   ![image](https://user-images.githubusercontent.com/92301646/142347998-406142f7-ff8b-4118-ae3a-b12785069639.png)
   
   ### Environment
   
   * your apisix-ingress-controller version (output of `apisix-ingress-controller version --long`);
   Version: 1.2.0
   Git SHA: no-git-module
   Go Version: go1.13.8
   Building OS/Arch: linux/amd64
   Running OS/Arch: linux/amd64
   * your Kubernetes cluster version (output of `kubectl version`);v1.18.10
   * if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (`uname -a`).
   Linux apisix-ingress-controller-8756d4d77-dvfzd 3.10.0-862.14.4.el7.x86_64 #1 SMP Wed Sep 26 15:12:11 UTC 2018 x86_64 Linux
   


-- 
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.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [apisix-ingress-controller] tokers commented on issue #758: request help: apisix-ingress-controller has many reported errors just like xxx not found

Posted by GitBox <gi...@apache.org>.
tokers commented on issue #758:
URL: https://github.com/apache/apisix-ingress-controller/issues/758#issuecomment-972717475


   These errors are harmless but I think they are intrusive. Maybe we can try to optimize the logging.
   
   cc @tao12345666333 


-- 
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.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #758: request help: apisix-ingress-controller has many reported errors just like xxx not found

Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #758:
URL: https://github.com/apache/apisix-ingress-controller/issues/758#issuecomment-972722973


   > apisix-ingress-controller has many reported errors,And there is no manual creation of resources via dashboard. Why are there so many upstream 404 and service not found here, are they traversing all the k8s services?
   
   The default configuration is to watch all namespaces, you can change the configuration so that it only watches certain specified namespaces.
   
   Of course, currently our logs also need to be optimized.


-- 
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.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [apisix-ingress-controller] suninuni commented on issue #758: request help: apisix-ingress-controller has many reported errors just like xxx not found

Posted by GitBox <gi...@apache.org>.
suninuni commented on issue #758:
URL: https://github.com/apache/apisix-ingress-controller/issues/758#issuecomment-1006342983


   These errors are also unnecessary, I did not create these resources. Watcher needs to distinguish between `failed` and `not found`.
   
   ```
   W0106 15:16:55.556649       1 reflector.go:441] pkg/mod/k8s.io/client-go@v0.22.4/tools/cache/reflector.go:167: watch of *v2beta3.ApisixConsumer ended with: an error on the server ("unable to decode an event from the watch stream: unable to decode watch event: no kind \"ApisixConsumer\" is registered for version \"apisix.apache.org/v2beta3\" in scheme \"pkg/runtime/scheme.go:100\"") has prevented the request from succeeding
   W0106 15:16:14.583021       1 reflector.go:441] pkg/mod/k8s.io/client-go@v0.22.4/tools/cache/reflector.go:167: watch of *v2beta3.ApisixClusterConfig ended with: an error on the server ("unable to decode an event from the watch stream: unable to decode watch event: no kind \"ApisixClusterConfig\" is registered for version \"apisix.apache.org/v2beta3\" in scheme \"pkg/runtime/scheme.go:100\"") has prevented the request from succeeding
   ```


-- 
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.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org