[WIP] feat: add gateway roles#3781
Conversation
Signed-off-by: Tadas Sutkaitis <[email protected]>
| # Ports used with additional prefix '4' to not overlap with ingress-nginx listeners. | ||
| # 'domain_name' is for example with Molecule only | ||
|
|
||
| gateway_listeners: |
There was a problem hiding this comment.
Mohammed Naser (@mnaser) Guilherme Steinmüller (@guilhermesteinmuller) this part need discussion. I think tcp/udp can be skiped in environments without designate. Right now we don't have such as flag. Listeners and hostnames.... This one most important here.
| # protocol: HTTP | ||
| # port: 80 | ||
|
|
||
| # Just for PoC disscusion: |
There was a problem hiding this comment.
For now only for PoC.
| vexxhost.ceph: ">=3.2.0" | ||
| atmosphere.common: ">=0.6.0" | ||
| vexxhost.kubernetes: ">=2.5.0" | ||
| vexxhost.kubernetes: 2.8.0 # temporary pin |
There was a problem hiding this comment.
Latest version is reverted for back compatibility.
| - http01: | ||
| ingress: | ||
| class: "{{ cluster_issuer_acme_http01_ingress_class }}" | ||
| gatewayHTTPRoute: |
There was a problem hiding this comment.
Needs testing with configuration like this: https://hannaske.net/blog/global-https-redirect-with-envoy-gateway/ when all http traffic is redirected to one of https listeners (ingress-nginx default behavior)
Signed-off-by: Tadas Sutkaitis <[email protected]>
|
recheck |
|
recheck |
…role dependencies Signed-off-by: Tadas Sutkaitis <[email protected]>
Signed-off-by: Tadas Sutkaitis <[email protected]>
Signed-off-by: Tadas Sutkaitis <[email protected]>
| - type: RequestRedirect | ||
| requestRedirect: | ||
| scheme: https | ||
| statusCode: 308 |
There was a problem hiding this comment.
finding: [spec.rules[0].filters[0].requestRedirect.statusCode: Unsupported value: 308: supported values: "301", "302",
https://gateway.envoyproxy.io/docs/tasks/traffic/http-redirect/ -> Note: 301 (default) and 302 are the only supported statusCodes.
Signed-off-by: Tadas Sutkaitis <[email protected]>
Signed-off-by: Tadas Sutkaitis <[email protected]>
No description provided.