Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[KIC] Fix TLSRoute documentation #8425

Open
2 tasks done
mlavacca opened this issue Feb 12, 2025 · 0 comments
Open
2 tasks done

[KIC] Fix TLSRoute documentation #8425

mlavacca opened this issue Feb 12, 2025 · 0 comments
Labels
bug Issues/PRs dealing with bugs in the docs team-k8s Kubernetes task tracking (including KIC,KGO)
Milestone

Comments

@mlavacca
Copy link
Member

mlavacca commented Feb 12, 2025

Where is the problem?

https://docs.konghq.com/kubernetes-ingress-controller/latest/guides/services/tls/

What happened?

The linked page has two different problems that need to be fixed:

  1. TLSRoute requires the Gateway API experimental channel and the GatewayAlpha feature gate enabled to properly work. We need to add them as prerequisites, similarly to what we do for TCPRoute in https://docs.konghq.com/kubernetes-ingress-controller/latest/guides/services/tcp/
  2. The Gateway using TLSRoute for TLS passthrough in the documentation uses port 443, which is inconsistent with the default value of the proxy port for TLS traffic (8899) we need to fix the Gateway port accordingly.

Code of Conduct and Community Expectations

  • I agree to follow this project's Code of Conduct
  • I agree to abide by the Community Expectations
@mlavacca mlavacca added bug Issues/PRs dealing with bugs in the docs team-k8s Kubernetes task tracking (including KIC,KGO) labels Feb 12, 2025
@mlavacca mlavacca added this to the KIC v3.5.x milestone Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues/PRs dealing with bugs in the docs team-k8s Kubernetes task tracking (including KIC,KGO)
Projects
None yet
Development

No branches or pull requests

1 participant