Skip to content

[WIP] feat: add gateway roles#3781

Open
Tadas Sutkaitis (fitbeard) wants to merge 7 commits intomainfrom
feat/add_gateway_role
Open

[WIP] feat: add gateway roles#3781
Tadas Sutkaitis (fitbeard) wants to merge 7 commits intomainfrom
feat/add_gateway_role

Conversation

@fitbeard
Copy link
Copy Markdown
Contributor

No description provided.

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:
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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:
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For now only for PoC.

Comment thread galaxy.yml
vexxhost.ceph: ">=3.2.0"
atmosphere.common: ">=0.6.0"
vexxhost.kubernetes: ">=2.5.0"
vexxhost.kubernetes: 2.8.0 # temporary pin
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Latest version is reverted for back compatibility.

- http01:
ingress:
class: "{{ cluster_issuer_acme_http01_ingress_class }}"
gatewayHTTPRoute:
Copy link
Copy Markdown
Contributor Author

@fitbeard Tadas Sutkaitis (fitbeard) Mar 31, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)

@fitbeard
Copy link
Copy Markdown
Contributor Author

recheck

@fitbeard
Copy link
Copy Markdown
Contributor Author

recheck

@ricolin Rico Lin (ricolin) self-requested a review April 9, 2026 02:16
- type: RequestRedirect
requestRedirect:
scheme: https
statusCode: 308
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant