Can anyone please help me out. I'm getting error while generating KONG client credentials on HTTP port 8000.

{ "error_description": "You must use HTTPS", "error": "access_denied" }

I have added trusted_ips = 0.0.0.0/0,::/0 in kong.conf also, but it didn't work.

Summary

As a summary of last discussion on our community slack and a result of my last investigations here: kumahq/kuma#2046 I think we should let us run kuma-init with --verbose flag which would show more information about iptables etc. without manually changing https://github.com/kumahq/kuma/blob/19a906795d47ff0006ab62e12211b48204ad5a0d/pkg/plugins/runtime/k8

A Kong SNI can only point to a single certificate. Per Kong/kubernetes-ingress-controller#1268 (comment), misconfigured Kubernetes resources can attempt to point an SNI to multiple certificates.

While we do avoid adding attached SNIs to new certificates, we do

Right now the tutorial is coherently designed, tested, and even documented. However, it doesn't build up in a way that's very beginner friendly. It establishes glom's value and then immediately uses it at an intermediate level.

I'd like it if it was a bit more drawn out to use basic features first and then add a multi-line Coalesce as the

So trying this out I've found that Pact.Net starts an additional service for both creation and verification of pacts.

Is there any specific reason other than that it hasn't been done because no one had time that this couldn't be done in memory with TestServer instead? That would completely eliminate the need for any sort of port allocation and the creation of additional actual live servers duri