Closed R3DRUN3 closed 1 year ago
@R3DRUN3 the issue was related to a wrong behavior in the Kong helm chart version we were using. The issue has been resolved upstream (https://github.com/Kong/charts/pull/705) and we are leveraging now Kong helm chart version 2.15.2. I made a test on a AKS cluster and everything's working correctly. Closing this issue.
After I installed Krateo on AKS (v1.24.6) I was not able to reach Krateo Web Portal trough Kong Load Balancer. This issue is basically the same as this one.
I was able to bypass the issue with the following steps:
Retrieve the LoadBalancer manifest and save it in a yaml file:
Open kong-svc.yaml and delete the "appProtocol" properties in the specs for example this:
becomes this:
Save and apply the new manifest:
Note
: Kong seems to have fixed this problem (PR merge in main), this should be solved in the next helm chart release