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.

Sign up for GitHub

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

Jump to bottom

add gatewayAPI equivalent to ingress to our helm charts #8261

Closed
lahabana opened this issue Nov 6, 2023 · 7 comments
Closed

add gatewayAPI equivalent to ingress to our helm charts #8261

lahabana opened this issue Nov 6, 2023 · 7 comments
Labels
area/k8s good first issue Good for newcomers kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@lahabana
Copy link
Contributor

lahabana commented Nov 6, 2023 •
edited
Loading

Description

Gateway API is GA and much better than ingress.
We should provide a way to create the equivalent of our cp-ingress in GatewayAPI style.
@lahabana lahabana added area/k8s triage/pending This issue will be looked at on the next triage meeting kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Nov 6, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Feb 5, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Feb 5, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@jakubdyszkiewicz jakubdyszkiewicz added good first issue Good for newcomers and removed triage/stale Inactive for some time. It will be triaged again labels Feb 5, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented May 6, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label May 6, 2024
@slonka slonka removed the triage/stale Inactive for some time. It will be triaged again label May 6, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Aug 5, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Aug 5, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lobkovilya lobkovilya removed the triage/stale Inactive for some time. It will be triaged again label Aug 5, 2024
@michaelbeaumont
Copy link
Contributor

@lahabana @lobkovilya should we do this really? I feel like we'd have to parameterize almost everything about the Gateway. Some users will want to use their own certs and do plaintext Gateway -> HTTP Kuma API, some may want to use Kuma's autogenerated certs. Then there's customizing the HTTPRoute...

Do users really badly not want to create their own Gateways/HTTPRoutes?
If we just want an option to expose the API in a really basic way, is a LoadBalancer Service not enough?

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Nov 4, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Nov 4, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lukidzi lukidzi added triage/pending This issue will be looked at on the next triage meeting and removed triage/stale Inactive for some time. It will be triaged again triage/accepted The issue was reviewed and is complete enough to start working on it labels Nov 12, 2024
@lukidzi
Copy link
Contributor

lukidzi commented Nov 12, 2024

triage: let's wait for now, there is ongoing work on a gatewayApi side to simplify it.

@lukidzi lukidzi added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Nov 12, 2024
@lukidzi
Copy link
Contributor

lukidzi commented Nov 12, 2024

Lets reopen once we feel is a time to get it done

@lukidzi lukidzi closed this as not planned Won't fix, can't repro, duplicate, stale Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/k8s good first issue Good for newcomers kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@lahabana @michaelbeaumont @slonka @jakubdyszkiewicz @lobkovilya @lukidzi