Tao Yi
Tao Yi
@Rockyjr-git Your configuration is right. Kong gateway itself is a REVERSE PROXY so configuration of rewrite URI does not affect your request from the browser to Kong gateway. So the...
@samaitegal TL;DR: There is a latency for KIC to load all the controlled resources but we cannot predict the latency now. Are there many resources (ingresses, services, pods, ...) controlled...
@samaitegal Is there any update on this issue now? If no more additional context is given in 7 days, we will close the issue as "won't fix".
@yang-wang11 KIC's webhook will validate ALL credentials configured in `KongConsumer`. If any of the credentials is invalid, KIC will reject this `KongConsumer`. If you want to rotate JWT key in...
Closed as won't fix because: - KIC 2.9.3 has been end of support since March 2024. - The behavior is expected where the old secret attached to `KongConsumer` is also...
@metheu could you please provide the versions of Kong and Kong ingress controller before/after the issue happens? Also, different consumers in different [Kong workspaces](https://docs.konghq.com/gateway/latest/kong-enterprise/#workspaces) not different k8s namespaces can share...
@metheu Another possibility is that you deployed different KIC and Kong gateway instances in different namespaces and KIC only controls the `KongConsumer` in its namespace and send them to managed...
@metheu If the `KongConsumer`s all have the same annotation `kubernetes.io/ingress.class`, they should have unique `username` each.
@javiramos1 Please confirm the version of your KIC and Kong gateway separately. The version `3.2` provided seems to be the version of Kong gateway. You can use the following command...
@javiramos1 Can you please provide the further information for us to triage? - The manifests of relevant `Ingress`es and `Service`s - The behavior of your backend services (Do they just...