feat: allow L4 upstream schemes (tcp/tls/udp) for stream backends by AlinsRan · Pull Request #449 · api7/api7-ingress-controller

AlinsRan · 2026-07-29T07:18:14Z

Description

Sync of apache/apisix-ingress-controller#2830 (fixes apache/apisix-ingress-controller#2803).

APISIX accepts tcp, tls and udp as upstream schemes for L4 proxying, and scheme: tls is what makes the gateway establish the TLS session with the upstream for a stream route (plain TCP in, TLS out).

Both ApisixUpstream.spec.scheme and BackendTrafficPolicy.spec.scheme restricted the value to the L7 set (http|https|grpc|grpcs), so this could only be configured through the Admin API.

The translation path already carries the scheme into the generated upstream for both entry points:

ApisixRoute stream backends merge the ApisixUpstream named after the backend Service;
Gateway API TCPRoute backends take the scheme from BackendTrafficPolicy.

So only CRD validation needed relaxing.

apiVersion: apisix.apache.org/v2
kind: ApisixUpstream
metadata:
  name: my-service     # same name as the backend Service
spec:
  scheme: tls

Tests

unit: TestTranslateApisixRouteStreamUpstreamScheme, TestTranslateTCPRouteUpstreamScheme
e2e: Test ApisixRoute With StreamRoute / TCP Proxy with TLS upstream and TCPRoute E2E Test / TCPRoute With BackendTrafficPolicy — both send plain HTTP over a TCP listener to nginx's TLS port and assert 200 + X-Port: 443, which only passes if the gateway performs the TLS handshake with the upstream.

Known follow-ups (not in this PR)

BackendTrafficPolicy.spec.scheme keeps +kubebuilder:default=http, so a policy attached only for load balancing still writes scheme: http onto an L4 upstream.
SchemeToPort has no entry for tls, so an externalNodes/ExternalName upstream without an explicit port defaults to 80.
portLevelSettings resets the top-level scheme for ports that do not set it.

Summary by CodeRabbit

New Features
- Added support for Layer 4 upstream schemes: tcp, tls, and udp.
- Expanded allowed scheme values for relevant CRDs so L4 can be used with stream-based routing.
Documentation
- Updated scheme field descriptions to clearly distinguish L7 (http, https, grpc, grpcs) vs L4 (tcp, tls, udp) behavior and limitations for HTTP routes.
Tests
- Added/expanded test coverage to validate upstream scheme handling for TCP/TLS/UDP scenarios, including end-to-end stream routing.

coderabbitai · 2026-07-29T07:18:41Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 876a2118-4fe7-4f61-bb19-6848638d595e

📥 Commits

Reviewing files that changed from the base of the PR and between 075d13c and 6e34fbf.

📒 Files selected for processing (10)

api/v1alpha1/backendtrafficpolicy_types.go
api/v2/apisixupstream_types.go
config/crd/bases/apisix.apache.org_apisixupstreams.yaml
config/crd/bases/apisix.apache.org_backendtrafficpolicies.yaml
docs/en/latest/reference/api-reference.md
internal/adc/translator/apisixroute_test.go
internal/adc/translator/l4route_test.go
internal/adc/translator/tcproute.go
test/e2e/crds/v2/streamroute.go
test/e2e/gatewayapi/tcproute.go

💤 Files with no reviewable changes (1)

internal/adc/translator/tcproute.go

🚧 Files skipped from review as they are similar to previous changes (9)

api/v2/apisixupstream_types.go
config/crd/bases/apisix.apache.org_backendtrafficpolicies.yaml
api/v1alpha1/backendtrafficpolicy_types.go
test/e2e/gatewayapi/tcproute.go
config/crd/bases/apisix.apache.org_apisixupstreams.yaml
test/e2e/crds/v2/streamroute.go
internal/adc/translator/apisixroute_test.go
internal/adc/translator/l4route_test.go
docs/en/latest/reference/api-reference.md

📝 Walkthrough

Walkthrough

The change expands upstream scheme validation and documentation to support tcp, tls, and udp, adds translator coverage for stream schemes, and adds end-to-end tests for TLS upstream routing through ApisixRoute and Gateway API TCPRoute.

Changes

L4 upstream scheme support

Layer / File(s)	Summary
Scheme contracts and documentation `api/...`, `config/crd/bases/...`, `docs/en/latest/reference/api-reference.md`	Scheme validation and descriptions now include `tcp`, `tls`, and `udp` for L4 proxy usage.
Stream translation coverage `internal/adc/translator/...`	Unit tests verify configured schemes and endpoint hosts for ApisixRoute and TCPRoute stream backends.
End-to-end TLS stream validation `test/e2e/crds/v2/streamroute.go`, `test/e2e/gatewayapi/tcproute.go`	End-to-end tests validate TLS upstream routing through ApisixRoute and Gateway API TCPRoute.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Suggested reviewers: nic-6443, shreemaan-abhishek

Sequence Diagram(s)

sequenceDiagram
  participant Route as ApisixRoute or TCPRoute
  participant Translator as Stream translator
  participant APISIX as APISIX upstream
  participant Backend as TLS backend
  Route->>Translator: Provide stream backend with scheme tls
  Translator->>APISIX: Configure scheme and endpoint host
  APISIX->>Backend: Open TLS connection
  Backend-->>APISIX: Return upstream response

🚥 Pre-merge checks | ✅ 5 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
E2e Test Quality Review	⚠️ Warning	The new e2e tests hit real services, but the CRD-based upstream test skips the usual acceptance wait, so it can race reconciliation; invalid-scheme coverage is also missing.	Use the existing acceptance helpers (`MustApplyAPIv2`/`ResourceApplied`) for `ApisixUpstream` and `BackendTrafficPolicy`, and add one negative validation test for an invalid scheme.

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: enabling L4 upstream schemes for stream backends.
Linked Issues check	✅ Passed	The PR satisfies `#2803` by allowing scheme tls in CRDs and propagating it for stream backends, with unit and e2e coverage.
Out of Scope Changes check	✅ Passed	The changes stay focused on L4 scheme support, schema updates, tests, and docs, with no clear unrelated additions.
Security Check	✅ Passed	Only CRD enum/docs/test updates; no secret handling, auth, ownership, or TLS-flag logic changes were introduced.

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch ee-2803-l4-upstream-scheme

_{Comment @coderabbitai help to get the list of available commands.}

github-actions · 2026-07-29T07:28:58Z

conformance test report - apisix mode

apiVersion: gateway.networking.k8s.io/v1
date: "2026-07-29T08:06:44Z"
gatewayAPIChannel: experimental
gatewayAPIVersion: v1.6.0
implementation:
  contact:
  - https://github.com/apache/apisix-ingress-controller/issues
  organization: APISIX
  project: apisix-ingress-controller
  url: https://github.com/apache/apisix-ingress-controller.git
  version: v2.0.0
kind: ConformanceReport
mode: default
profiles:
- core:
    result: partial
    skippedTests:
    - HTTPRouteHTTPSListener
    - HTTPRouteInvalidBackendRefUnknownKind
    - HTTPRouteInvalidCrossNamespaceBackendRef
    - HTTPRouteInvalidNonExistentBackendRef
    - HTTPRouteListenerHostnameMatching
    - HTTPRouteMultipleGateways
    - HTTPRouteNoBackendRefs
    statistics:
      Failed: 0
      Passed: 30
      Skipped: 7
  extended:
    result: partial
    skippedTests:
    - HTTPRouteRedirectPortAndScheme
    statistics:
      Failed: 0
      Passed: 12
      Skipped: 1
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayPort8080
    - HTTPRouteBackendProtocolWebSocket
    - HTTPRouteDestinationPortMatching
    - HTTPRouteHostRewrite
    - HTTPRouteMethodMatching
    - HTTPRoutePathRewrite
    - HTTPRoutePortRedirect
    - HTTPRouteQueryParamMatching
    - HTTPRouteRequestMirror
    - HTTPRouteResponseHeaderModification
    - HTTPRouteSchemeRedirect
    unsupportedFeatures:
    - BackendTLSPolicy
    - BackendTLSPolicySANValidation
    - GatewayBackendClientCertificate
    - GatewayFrontendClientCertificateValidation
    - GatewayFrontendClientCertificateValidationInsecureFallback
    - GatewayHTTPListenerIsolation
    - GatewayHTTPSListenerDetectMisdirectedRequests
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - HTTPRoute303RedirectStatusCode
    - HTTPRoute307RedirectStatusCode
    - HTTPRoute308RedirectStatusCode
    - HTTPRouteBackendProtocolH2C
    - HTTPRouteBackendRequestHeaderModification
    - HTTPRouteBackendTimeout
    - HTTPRouteCORS
    - HTTPRouteNamedRouteRule
    - HTTPRouteParentRefPort
    - HTTPRoutePathRedirect
    - HTTPRouteRequestMultipleMirrors
    - HTTPRouteRequestPercentageMirror
    - HTTPRouteRequestTimeout
    - HTTPRouteRetry
    - HTTPRouteRetryBackendTimeout
    - HTTPRouteRetryConnectionError
    - ListenerSet
  name: GATEWAY-HTTP
  summary: Core tests partially succeeded with 7 test skips. Extended tests partially
    succeeded with 1 test skips.
- core:
    result: partial
    skippedTests:
    - GRPCRouteListenerHostnameMatching
    statistics:
      Failed: 0
      Passed: 14
      Skipped: 1
  extended:
    result: success
    statistics:
      Failed: 0
      Passed: 1
      Skipped: 0
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayPort8080
    unsupportedFeatures:
    - GatewayBackendClientCertificate
    - GatewayFrontendClientCertificateValidation
    - GatewayFrontendClientCertificateValidationInsecureFallback
    - GatewayHTTPListenerIsolation
    - GatewayHTTPSListenerDetectMisdirectedRequests
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - ListenerSet
  name: GATEWAY-GRPC
  summary: Core tests partially succeeded with 1 test skips. Extended tests succeeded.
- core:
    result: partial
    skippedTests:
    - TLSRouteHostnameIntersection
    - TLSRouteInvalidBackendRefNonexistent
    - TLSRouteInvalidBackendRefUnknownKind
    - TLSRouteSimpleSameNamespace
    statistics:
      Failed: 0
      Passed: 16
      Skipped: 4
  extended:
    result: partial
    skippedTests:
    - TLSRouteTerminateSimpleSameNamespace
    statistics:
      Failed: 0
      Passed: 3
      Skipped: 1
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayPort8080
    - TLSRouteModeTerminate
    unsupportedFeatures:
    - GatewayBackendClientCertificate
    - GatewayFrontendClientCertificateValidation
    - GatewayFrontendClientCertificateValidationInsecureFallback
    - GatewayHTTPListenerIsolation
    - GatewayHTTPSListenerDetectMisdirectedRequests
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - ListenerSet
    - TLSRouteModeMixed
  name: GATEWAY-TLS
  summary: Core tests partially succeeded with 4 test skips. Extended tests partially
    succeeded with 1 test skips.
succeededProvisionalTests:
- GatewayOptionalAddressValue

github-actions · 2026-07-29T07:29:19Z

conformance test report - apisix-standalone mode

apiVersion: gateway.networking.k8s.io/v1
date: "2026-07-29T08:07:03Z"
gatewayAPIChannel: experimental
gatewayAPIVersion: v1.6.0
implementation:
  contact:
  - https://github.com/apache/apisix-ingress-controller/issues
  organization: APISIX
  project: apisix-ingress-controller
  url: https://github.com/apache/apisix-ingress-controller.git
  version: v2.0.0
kind: ConformanceReport
mode: default
profiles:
- core:
    result: partial
    skippedTests:
    - HTTPRouteHTTPSListener
    - HTTPRouteInvalidBackendRefUnknownKind
    - HTTPRouteInvalidCrossNamespaceBackendRef
    - HTTPRouteInvalidNonExistentBackendRef
    - HTTPRouteListenerHostnameMatching
    - HTTPRouteMultipleGateways
    - HTTPRouteNoBackendRefs
    statistics:
      Failed: 0
      Passed: 30
      Skipped: 7
  extended:
    result: partial
    skippedTests:
    - HTTPRouteRedirectPortAndScheme
    statistics:
      Failed: 0
      Passed: 12
      Skipped: 1
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayPort8080
    - HTTPRouteBackendProtocolWebSocket
    - HTTPRouteDestinationPortMatching
    - HTTPRouteHostRewrite
    - HTTPRouteMethodMatching
    - HTTPRoutePathRewrite
    - HTTPRoutePortRedirect
    - HTTPRouteQueryParamMatching
    - HTTPRouteRequestMirror
    - HTTPRouteResponseHeaderModification
    - HTTPRouteSchemeRedirect
    unsupportedFeatures:
    - BackendTLSPolicy
    - BackendTLSPolicySANValidation
    - GatewayBackendClientCertificate
    - GatewayFrontendClientCertificateValidation
    - GatewayFrontendClientCertificateValidationInsecureFallback
    - GatewayHTTPListenerIsolation
    - GatewayHTTPSListenerDetectMisdirectedRequests
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - HTTPRoute303RedirectStatusCode
    - HTTPRoute307RedirectStatusCode
    - HTTPRoute308RedirectStatusCode
    - HTTPRouteBackendProtocolH2C
    - HTTPRouteBackendRequestHeaderModification
    - HTTPRouteBackendTimeout
    - HTTPRouteCORS
    - HTTPRouteNamedRouteRule
    - HTTPRouteParentRefPort
    - HTTPRoutePathRedirect
    - HTTPRouteRequestMultipleMirrors
    - HTTPRouteRequestPercentageMirror
    - HTTPRouteRequestTimeout
    - HTTPRouteRetry
    - HTTPRouteRetryBackendTimeout
    - HTTPRouteRetryConnectionError
    - ListenerSet
  name: GATEWAY-HTTP
  summary: Core tests partially succeeded with 7 test skips. Extended tests partially
    succeeded with 1 test skips.
- core:
    result: partial
    skippedTests:
    - GRPCRouteListenerHostnameMatching
    statistics:
      Failed: 0
      Passed: 14
      Skipped: 1
  extended:
    result: success
    statistics:
      Failed: 0
      Passed: 1
      Skipped: 0
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayPort8080
    unsupportedFeatures:
    - GatewayBackendClientCertificate
    - GatewayFrontendClientCertificateValidation
    - GatewayFrontendClientCertificateValidationInsecureFallback
    - GatewayHTTPListenerIsolation
    - GatewayHTTPSListenerDetectMisdirectedRequests
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - ListenerSet
  name: GATEWAY-GRPC
  summary: Core tests partially succeeded with 1 test skips. Extended tests succeeded.
- core:
    result: partial
    skippedTests:
    - TLSRouteHostnameIntersection
    - TLSRouteInvalidBackendRefNonexistent
    - TLSRouteInvalidBackendRefUnknownKind
    - TLSRouteSimpleSameNamespace
    statistics:
      Failed: 0
      Passed: 16
      Skipped: 4
  extended:
    result: partial
    skippedTests:
    - TLSRouteTerminateSimpleSameNamespace
    statistics:
      Failed: 0
      Passed: 3
      Skipped: 1
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayPort8080
    - TLSRouteModeTerminate
    unsupportedFeatures:
    - GatewayBackendClientCertificate
    - GatewayFrontendClientCertificateValidation
    - GatewayFrontendClientCertificateValidationInsecureFallback
    - GatewayHTTPListenerIsolation
    - GatewayHTTPSListenerDetectMisdirectedRequests
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - ListenerSet
    - TLSRouteModeMixed
  name: GATEWAY-TLS
  summary: Core tests partially succeeded with 4 test skips. Extended tests partially
    succeeded with 1 test skips.
succeededProvisionalTests:
- GatewayOptionalAddressValue

github-actions · 2026-07-29T07:48:04Z

conformance test report

apiVersion: gateway.networking.k8s.io/v1
date: "2026-07-29T08:25:12Z"
gatewayAPIChannel: experimental
gatewayAPIVersion: v1.6.0
implementation:
  contact:
  - https://github.com/apache/apisix-ingress-controller/issues
  organization: APISIX
  project: apisix-ingress-controller
  url: https://github.com/apache/apisix-ingress-controller.git
  version: v2.0.0
kind: ConformanceReport
mode: default
profiles:
- core:
    failedTests:
    - GatewayModifyListeners
    result: failure
    statistics:
      Failed: 1
      Passed: 14
      Skipped: 0
  extended:
    result: success
    statistics:
      Failed: 0
      Passed: 1
      Skipped: 0
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayPort8080
    unsupportedFeatures:
    - GatewayBackendClientCertificate
    - GatewayFrontendClientCertificateValidation
    - GatewayFrontendClientCertificateValidationInsecureFallback
    - GatewayHTTPListenerIsolation
    - GatewayHTTPSListenerDetectMisdirectedRequests
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - ListenerSet
  name: GATEWAY-GRPC
  summary: Core tests failed with 1 test failures. Extended tests succeeded.
- core:
    failedTests:
    - GatewayModifyListeners
    - TLSRouteHostnameIntersection
    - TLSRouteInvalidBackendRefNonexistent
    - TLSRouteInvalidBackendRefUnknownKind
    - TLSRouteSimpleSameNamespace
    result: failure
    statistics:
      Failed: 5
      Passed: 15
      Skipped: 0
  extended:
    failedTests:
    - TLSRouteTerminateSimpleSameNamespace
    result: failure
    statistics:
      Failed: 1
      Passed: 3
      Skipped: 0
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayPort8080
    - TLSRouteModeTerminate
    unsupportedFeatures:
    - GatewayBackendClientCertificate
    - GatewayFrontendClientCertificateValidation
    - GatewayFrontendClientCertificateValidationInsecureFallback
    - GatewayHTTPListenerIsolation
    - GatewayHTTPSListenerDetectMisdirectedRequests
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - ListenerSet
    - TLSRouteModeMixed
  name: GATEWAY-TLS
  summary: Core tests failed with 5 test failures. Extended tests failed with 1 test
    failures.
- core:
    failedTests:
    - GatewayModifyListeners
    - HTTPRouteMultipleGateways
    - HTTPRouteNoBackendRefs
    result: failure
    skippedTests:
    - HTTPRouteHTTPSListener
    statistics:
      Failed: 3
      Passed: 33
      Skipped: 1
  extended:
    result: partial
    skippedTests:
    - HTTPRouteRedirectPortAndScheme
    statistics:
      Failed: 0
      Passed: 12
      Skipped: 1
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayPort8080
    - HTTPRouteBackendProtocolWebSocket
    - HTTPRouteDestinationPortMatching
    - HTTPRouteHostRewrite
    - HTTPRouteMethodMatching
    - HTTPRoutePathRewrite
    - HTTPRoutePortRedirect
    - HTTPRouteQueryParamMatching
    - HTTPRouteRequestMirror
    - HTTPRouteResponseHeaderModification
    - HTTPRouteSchemeRedirect
    unsupportedFeatures:
    - BackendTLSPolicy
    - BackendTLSPolicySANValidation
    - GatewayBackendClientCertificate
    - GatewayFrontendClientCertificateValidation
    - GatewayFrontendClientCertificateValidationInsecureFallback
    - GatewayHTTPListenerIsolation
    - GatewayHTTPSListenerDetectMisdirectedRequests
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - HTTPRoute303RedirectStatusCode
    - HTTPRoute307RedirectStatusCode
    - HTTPRoute308RedirectStatusCode
    - HTTPRouteBackendProtocolH2C
    - HTTPRouteBackendRequestHeaderModification
    - HTTPRouteBackendTimeout
    - HTTPRouteCORS
    - HTTPRouteNamedRouteRule
    - HTTPRouteParentRefPort
    - HTTPRoutePathRedirect
    - HTTPRouteRequestMultipleMirrors
    - HTTPRouteRequestPercentageMirror
    - HTTPRouteRequestTimeout
    - HTTPRouteRetry
    - HTTPRouteRetryBackendTimeout
    - HTTPRouteRetryConnectionError
    - ListenerSet
  name: GATEWAY-HTTP
  summary: Core tests failed with 3 test failures. Extended tests partially succeeded
    with 1 test skips.
succeededProvisionalTests:
- GatewayOptionalAddressValue

APISIX accepts `tcp`, `tls` and `udp` as upstream schemes for L4 proxying, but both `ApisixUpstream.spec.scheme` and `BackendTrafficPolicy.spec.scheme` restricted the value to the L7 set, so an upstream that requires TLS from APISIX (plain TCP in, TLS out) could only be configured through the Admin API. The translation path already carries the scheme to the generated upstream for both ApisixRoute stream backends and Gateway API TCPRoute backends, so only the CRD validation needed to be relaxed. Sync of apache/apisix-ingress-controller#2830 (fixes apache/apisix-ingress-controller#2803).

jarvis9443 · 2026-07-30T02:44:58Z

+	// For L4 proxy, it can be `tcp`, `tls`, or `udp`.
+	// The L4 values apply to stream routes only; using them for an HTTP route
+	// makes the upstream unreachable.
+	// +kubebuilder:validation:Enum=http;https;grpc;grpcs;tcp;tls;udp;


[P1] Update the Helm-bundled CRDs with this enum

The CRDs bundled in api7/api7-helm-chart still allow only http, https, grpc, and grpcs for both ApisixUpstream and BackendTrafficPolicy. A standard Helm installation will therefore have the API server reject tcp/tls/udp before this controller sees the resource. Please provide the paired Helm chart update and release dependency with this CRD change.

jarvis9443 · 2026-07-30T02:44:58Z

+			if framework.ProviderType == framework.ProviderTypeAPI7EE {
+				// The API7 EE Admin API only accepts tcp/udp as the upstream scheme
+				// of a stream service.
+				Skip("scheme: tls is not supported by the API7 EE provider")


[P1] Keep the API7EE provider path working

The CRD now accepts scheme: tls, but the API7EE Control Plane currently permits only tcp and udp for stream-service upstreams. The controller therefore accepts this Kubernetes object and then fails to sync it through the API7EE provider; skipping the only API7EE end-to-end path hides that broken behavior. Please land the corresponding Control Plane support and run this case without the skip, or keep tls unavailable in this repository until that provider supports it.

Landing the Control Plane support: api7/api7ee-3-control-plane#2869.

The restriction was not a data plane limitation — the APISIX schema bundled in the Dashboard already allows tcp/tls/udp. Two Control Plane validations narrowed the stream set to tcp/udp: the StreamScheme enum in the OpenAPI schema (upstream embedded in a stream service) and validateUpstreamScheme() (standalone upstream API, where the body is oneOf(HTTPUpstream, StreamUpstream) so the spec cannot tell the service types apart). Both accept tls now.

I will drop the Skip() here and run the API7EE case once #2869 is merged and a CP image with it is available.

AlinsRan force-pushed the ee-2803-l4-upstream-scheme branch from 075d13c to 6e34fbf Compare July 29, 2026 07:58

AlinsRan self-assigned this Jul 30, 2026

jarvis9443 reviewed Jul 30, 2026

View reviewed changes

shreemaan-abhishek approved these changes Jul 30, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat: allow L4 upstream schemes (tcp/tls/udp) for stream backends - #449

feat: allow L4 upstream schemes (tcp/tls/udp) for stream backends#449
AlinsRan wants to merge 1 commit into
masterfrom
ee-2803-l4-upstream-scheme

AlinsRan commented Jul 29, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

coderabbitai Bot commented Jul 29, 2026 •

edited

Loading

Walkthrough

Changes

Sequence Diagram(s)

❌ Failed checks (1 warning)

Uh oh!

github-actions Bot commented Jul 29, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Jul 29, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Jul 29, 2026 •

edited

Loading

Uh oh!

jarvis9443 Jul 30, 2026

Uh oh!

jarvis9443 Jul 30, 2026

Uh oh!

AlinsRan Jul 30, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

AlinsRan commented Jul 29, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Tests

Known follow-ups (not in this PR)

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented Jul 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Sequence Diagram(s)

❌ Failed checks (1 warning)

Uh oh!

github-actions Bot commented Jul 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

conformance test report - apisix mode

Uh oh!

github-actions Bot commented Jul 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

conformance test report - apisix-standalone mode

Uh oh!

github-actions Bot commented Jul 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

conformance test report

Uh oh!

jarvis9443 Jul 30, 2026

Choose a reason for hiding this comment

Uh oh!

jarvis9443 Jul 30, 2026

Choose a reason for hiding this comment

Uh oh!

AlinsRan Jul 30, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

AlinsRan commented Jul 29, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Jul 29, 2026 •

edited

Loading

github-actions Bot commented Jul 29, 2026 •

edited

Loading

github-actions Bot commented Jul 29, 2026 •

edited

Loading

github-actions Bot commented Jul 29, 2026 •

edited

Loading