abdallah
abdallah
Thank you so much @cmorten @kitsonk for the detailed help. I should've noticed the allowlist in Envoy, I'll give that a go! Happy to close this issue 😊
FYI; this issue also occurs when one of the response codes does not have any content field defined and another response code does.
@thim81 if both status codes have text/plain or any other content-type (as long as they're the same), they work just fine. So Postman does supports different types of content type....
Hi @savage-alex @thim81 , I didn't configure portman and using it with default config I suppose. I recorded a video here going through the issue if that could help https://www.loom.com/share/a99022b031c54cac92409fde3b0f94f2
@thim81 thank you SO much!!!!!
Thanks! Feel free to close the issue if needed 👍🏽
We probably should keep on installing as this is a warning and shouldn't block the flow... but perhaps it's cumbersome to parse through the warning and get to the json...
The warning comes when working with a GKE cluster, and it will definitely appear to some users as they migrate to the new authentication of kubectl version 1.25 https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke. If...
I think we'll try to support this use case through OpenAPI Overlays
Chris: the auth upstream shouldn't be cached, but the app upstream should be cached