1
Kong for Kubernetes config generation improvements
Source: Kong/insomnia#3752 · opened by @develohpanda
• If multiple Ingress documents exist, they must have unique names. Otherwise, running kubectl will overwrite the previous one - #2163 • Consider adding [konghq.com/protocols]( annotation explicitly, to retain more routing information if a service can be both http and https. - Currently, a server being http or https doesn't do anything to the ingress document (as the protocol is stripped). It is only the existence of a tls section that modifies the Ingress document. - How should the annotation be controlled? What decides whether the annotation says http, or http,https, or https? • Generate a k8s service manifest with unique names - a service can be for [multiple ports]( (ie. support both http and https) - The 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 simplifie…
No pledges yet. Be the first to back this.
Comments
Similar requests
Tagging Kong Entities in O2K
1 vote · 0 comments
support for command line environment variables
7 votes · 0 comments
Allow usage of server variables other than default
1 vote · 0 comments
Support uploading Specs to Kong Konnect
1 vote · 0 comments
OpenAPI Extension for Kong Enterprise Workspace
1 vote · 0 comments
No comments yet.