Next line returns 200 as status https://github.com/Kong/kong/blob/c817fada7a514d84f6e0aab7461605c71bf3a841/kong/plugins/cors/handler.lua#L13

Internet says it should return 204:

• https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request
• https://docs.microsoft.com/en-us/aspnet/core/security/cors?view=aspnetcore-3.1#preflight-requests

Internet changed its mind since 2018 https://

Summary

Today our testing infrastructure relies heavily on KinD which is a convenient way to run ephemeral K8s clusters locally. However, since it packs a full K8s distro, it tends to be slow especially when several clusters are run in parallel (e.g. our multi-zone). We surely know docker can do better as spinning a couple of Kuma universal cluster

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

We have upgrade the Kong Ingress controller from version 0.8.1 to 1.0.0, and we see some difference in error reporting for non found plugin info.

Version 0.8.1

E0107 21:02:23.092573 1 parser.go:1331] fetching KongPlugin 'tme-ns-cms-uat/oidc-auth-acc': no KongPlugin or KongClusterPlugin was found

Version 1.0.0

time="2021-01-07T21:04:29Z" level=error msg="failed to fetch KongPlugi

As part of the process of making the Pact docs more user friendly, we'd like to start writing feature documentation once, and providing code examples for each of the languages, rather than everyone having to write the same docs over and over again in each language.

The documentation for the consumer version selectors can be our first opportunity to give this approach a try. I have written the beh