Conversation
0b05088 to
e520182
Compare
ad885c0 to
11ccd59
Compare
04d55a5 to
432ff85
Compare
939d351 to
b1caf52
Compare
4c7d095 to
1fa2195
Compare
4150c01 to
994e42a
Compare
b5fd1af to
ba9ea8f
Compare
bb3e82c to
f17e79e
Compare
c7133f0 to
99522b7
Compare
…steners Adds a new "envoygateway" ingress controller for exposing Kafka external listeners, built on the Kubernetes Gateway API (https://gateway.envoyproxy.io/). Enable it per external listener with `spec.ingressController: envoygateway` and configure it via the new `envoyGatewayConfig` field. The `ingressController` enum is now `envoy;contour;envoygateway`. The previous istio-based ingress relied on banzaicloud/istio-operator, which is EOL/unmaintained (already removed on master); Envoy Gateway is a CNCF-backed, actively maintained Gateway API implementation. Changes: - New envoygateway resource reconciler (pkg/resources/envoygateway): generates Gateway + TCPRoute, with optional TLS. - New EnvoyGatewayIngressConfig API type + `ingressController: envoygateway`. - Refactor external listener status handling into a per-listener dispatcher (createListenerStatuses) so ingress types plug in cleanly. - Sample manifests for ZooKeeper and KRaft modes. - Additional unit tests (envoy resource, k8sutil, nodeport external access) and e2e coverage (install/produce/consume/uninstall with Envoy Gateway ingress in both ZooKeeper and KRaft modes, Envoy Gateway Helm chart v1.5.4). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a new Envoy Gateway ingress controller for exposing Kafka external
listeners, built on the Kubernetes Gateway API (https://gateway.envoyproxy.io/).
Enable it per external listener with
spec.ingressController: envoygatewayandconfigure it via the new
envoyGatewayConfigfield. TheingressControllerenum is now
envoy;contour;envoygateway.Why
The previous istio-based ingress relied on
banzaicloud/istio-operator, which isEOL/unmaintained (already removed on master). Envoy Gateway is a CNCF-backed,
actively maintained Gateway API implementation.
Changes
envoygatewayresource reconciler (pkg/resources/envoygateway):generates Gateway + TCPRoute, with optional TLS.
EnvoyGatewayIngressConfigAPI type +ingressController: envoygateway.Testing
webhook port-collision validation.
ingress in both ZooKeeper and KRaft modes (Envoy Gateway Helm chart v1.5.4).