apisix-ingress-controller
apisix-ingress-controller copied to clipboard
apache
APISIX Ingress Controller for Kubernetes
### Current Behavior When using standalone mode, Control API does not return health check data.  ### Expected Behavior When using etcd, Control API returns meaningful health check data: ...
### Current Behavior **Current Behavior** **Summary** After a workload pod restarts and receives a new IP, APISIX continues routing to the old endpoint. In addition, route-level custom plugins (auth/credentials) are...
### Current Behavior When deploying ingress-controller and specifying only `apisix.adminService.name` and `apisix.adminService.namespace` the resulting endpoint created is invalid. It points to: `http://[apisix.adminService.name]+[apisix.adminService.name]+".svc:"+[apisix.adminService.port]` ### Expected Behavior it's supposed to point to:...
### Current Behavior After upgrading to ingress-controller v2, annotations that previously enabled specific plugins or settings (e.g. k8s.apisix.apache.org/plugin-config-name) are no longer interpreted. The same manifests worked correctly in v1. ###...
### Current Behavior I have installed APISIX in decoupled mode of deployment. I have also deployed apisix-ingress-controller with image [2.0.0-rc2]. I have used the admin API to create a consumer....
### Description I have triying to configurate apisix in minikube (before to dpeloy it in my real cluster). I have using the helm chart with kustomize. I have configured a...
We should add more and more unit test cases for Controllers like ApisixUpstream, ApisixRoute, ApisixTLS.
Just like ingress-nginx: https://github.com/kubernetes/ingress-nginx/blob/master/docs/kubectl-plugin.md.