envoyproxy / envoyproxy/gateway
Usage of Envoy Gateway on OpenShift environments (Usage of Envoy Gateway with older Gateway API versions)
- Dominant language
- Go
- Stars
- 3k
- Forks
- 864
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 140
Description
*Description*:
Hi everyone, we are using Envoy Gateway on Kubernetes for Ingress traffic and so far it worked well. Our problem is, we also need to support OpenShift environments, and for us it would be very nice to be able to use Envoy Gateway in OpenShift too, but unfortunately at this point it seems it is not possible due to Gateway API version discrepancy.
Can you please share your vision on this issue, do you have plans to maybe somehow conform to OpenShift environments, or maybe you have some other suggestions how you see people should deal with this issue? For us it looks like there are no plans to support OpenShift environments in Envoy Gateway, so it seems we have to use OpenShift-provided implementation. We just would like to know your opinion/vision on this, because I was not able to find it stated explicitly/publicly anywhere
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the issue's OpenShift and older Gateway API version constraints, then compare them with Envoy Gateway's documented compatibility. The issue does not name files, tests, or an implementation entry point; it is complete only when maintainers define a supported approach or explicit compatibility plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- api, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100