Add ingress.useExisting value #44009
Conversation
|
The PR changelog entry failed validation: The changelog entry must start with a letter. |
github-actions
bot
requested review from
marcoandredinis,
mmcallister,
ptgott,
r0mant,
tigrato,
xinding33 and
zmb3
Co-authored-by: Marco Dinis <marco.dinis@goteleport.com>
|
🤖 Vercel preview here: https://docs-6zb79ymz7-goteleport.vercel.app/docs/ver/preview |
|
🤖 Vercel preview here: https://docs-7fxzgpwhx-goteleport.vercel.app/docs/ver/preview |
Co-authored-by: Gus Luxton <gus@goteleport.com>
|
🤖 Vercel preview here: https://docs-geu0mwuzq-goteleport.vercel.app/docs/ver/preview |
public-teleport-github-review-bot
bot
removed request for
tigrato,
mmcallister,
zmb3 and
xinding33
public-teleport-github-review-bot
bot
removed the request for review
from ptgott
| `values.yaml` example: | ||
|
|
||
| ```yaml | ||
| ingress: |
There was a problem hiding this comment.
should we start renaming this to the gateway api now that ingress api is frozen for quite some time?
There was a problem hiding this comment.
Last time I checked the gateway API is optional, its CRDs are not here by default. This makes the adoption for generic tools like us very hard.
I can extend the ingress.useExisting documentation that users can manage their own ingress, or HTTProute if they want. Using TCPRoute is roughly equivalent to using a ServiceLB and we must not allow self-signed+replication in this setup. TLSRoute experience will depend on the configuration. I don't think we can just replace "ingress" by "gateway API" as the new gwapi is way more powerful and allows user to shoot themselves in the foot in brand new ways.
Users are also thinking about ingress when they need to expose a service (and they also sadly don't consider L4 LoadBalancer Services, this just makes Teleport slower and more complex to deploy). I think ingress is the name everyone is looking for and we should not rename this section.
Co-authored-by: Tiago Silva <tiago.silva@goteleport.com>
|
🤖 Vercel preview here: https://docs-nvf7czn6s-goteleport.vercel.app/docs/ver/preview |
|
🤖 Vercel preview here: https://docs-8wi4p3ir7-goteleport.vercel.app/docs/ver/preview |
|
🤖 Vercel preview here: https://docs-icogpui7x-goteleport.vercel.app/docs/ver/preview |
|
@hugoShaka See the table below for backport results.
|
This PR adds a value allowing users to indicate they want to manage their own ingress but still want Teleport configured in ingress mode.
Changelog: The
teleport-clusterchart can now use existing ingresses instead of creating its own.