You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 7, 2024. It is now read-only.
HI:
kong version: 0.14.1, konga version: 0.13.0, I use key_auth for certification.
After I have created a connection rule, I click ACTIVATE button to show that I can connect to the service normally, But when I click on the list of services, it appears empty.
And then I manually accessed this url. curl -X GET https://xxx.xxx.com/api/admin-api/services?apikey=xxxxx, It returns complete service list information.
And what I need to say is that our domain name was created through ingress-gcp.
So I want to ask next, what do I need to do?
The text was updated successfully, but these errors were encountered:
On the other hand, I use LoadBalancer to directly open port 80/443 of kong, The konga can connect to the kong properly and manage the kong properly. So I also need to know whether it's konga or ingress-gcp, so I want to know how to tell if Konga is normal.
@linydquantil , I haven't had the chance to use Konga with Kong on a k8 cluster using ingress controller.
I'll tag this issue in case someone else has experiences something like that.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
HI:
kong version: 0.14.1, konga version: 0.13.0, I use key_auth for certification.
After I have created a connection rule, I click ACTIVATE button to show that I can connect to the service normally, But when I click on the list of services, it appears empty.
And then I manually accessed this url. curl -X GET https://xxx.xxx.com/api/admin-api/services?apikey=xxxxx, It returns complete service list information.
And what I need to say is that our domain name was created through ingress-gcp.
So I want to ask next, what do I need to do?
The text was updated successfully, but these errors were encountered: