Kong for Kubernetes config generation improvements #3752
Unanswered
develohpanda
asked this question in
Ideas
Replies: 2 comments
-
Server URL protocol. We should use
True. This modifies the K8s behavior, which would be nice if K4K8s converted this to annotations for Kong. The
My understanding was that K4K8s did this under the hood, if that's not the case, this would be ideal.
Let's meet tomorrow to discuss this in depth |
Beta Was this translation helpful? Give feedback.
0 replies
-
What about a service that is defined as: services:
- url: {scheme}://api.insomnia.rest
variables:
scheme:
default: 'http'
enum:
- 'http'
- 'https' |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Ingress
documents exist, they must have unique names. Otherwise, runningkubectl
will overwrite the previous one - k4k8s - ingress document name must be unique #2163konghq.com/protocols
annotation explicitly, to retain more routing information if a service can be bothhttp
andhttps
.tls
section that modifies the Ingress document.insomnia/packages/openapi-2-kong/src/kubernetes/index.js
Lines 160 to 175 in 75a129c
http
, orhttp,https
, orhttps
?http
andhttps
)konghq.com/plugins
annotation can be applied to a service specifically. If the same plugin is applied to a service and the ingress document, which takes precendence? (If this behaves as expected, our conversion implementation can be simplified).OAS.services
)konghq.com/path
on a service, as a routing prefix 🤔konghq.com/path = "/ds-api"
{service}-{plugin-name}-{suffix}
Beta Was this translation helpful? Give feedback.
All reactions