Skip to content

v.1.4.0: inferred supported features reported as unsupported in conformance results #4112

@snorwin

Description

@snorwin

What happened:
The inferred extended supported features from the GatewayClass are still being reported as unsupportedFeatures in the conformance report, even though the tests for them passed successfully.

What you expected to happen:
The features defined on the GatewayClass as supportedFeatures, for example:

   supportedFeatures:
    - name: Gateway
    - name: GatewayInfrastructurePropagation
    - name: GatewayPort8080
    - name: HTTPRoute
    - name: HTTPRouteBackendProtocolH2C
    - name: HTTPRouteBackendProtocolWebSocket
    - name: HTTPRouteBackendTimeout
    - name: HTTPRouteCORS
    - name: HTTPRouteDestinationPortMatching
    - name: HTTPRouteHostRewrite
    - name: HTTPRouteMethodMatching
    - name: HTTPRouteNamedRouteRule
    - name: HTTPRouteParentRefPort
    - name: HTTPRoutePathRedirect
    - name: HTTPRoutePathRewrite
    - name: HTTPRoutePortRedirect
    - name: HTTPRouteQueryParamMatching
    - name: HTTPRouteRequestTimeout
    - name: HTTPRouteResponseHeaderModification
    - name: HTTPRouteSchemeRedirect
    - name: ReferenceGrant

Which means should appear under the list of supported features in the conformance report. However, despite all related tests passing, they are incorrectly reported as unsupported:

  extended:
    result: success
    statistics:
      Failed: 0
      Passed: 20
      Skipped: 0
    unsupportedFeatures:
    - GatewayAddressEmpty
    - GatewayHTTPListenerIsolation
    - GatewayInfrastructurePropagation
    - GatewayPort8080
    - GatewayStaticAddresses
    - HTTPRouteBackendProtocolH2C
    - HTTPRouteBackendProtocolWebSocket
    - HTTPRouteBackendRequestHeaderModification
    - HTTPRouteBackendTimeout
    - HTTPRouteCORS
    - HTTPRouteDestinationPortMatching
    - HTTPRouteHostRewrite
    - HTTPRouteMethodMatching
    - HTTPRouteNamedRouteRule
    - HTTPRouteParentRefPort
    - HTTPRoutePathRedirect
    - HTTPRoutePathRewrite
    - HTTPRoutePortRedirect
    - HTTPRouteQueryParamMatching
    - HTTPRouteRequestMirror
    - HTTPRouteRequestMultipleMirrors
    - HTTPRouteRequestPercentageMirror
    - HTTPRouteRequestTimeout
    - HTTPRouteResponseHeaderModification
    - HTTPRouteSchemeRedirect

How to reproduce it (as minimally and precisely as possible):
Run the conformance tests without explicitly setting any supported features.

Anything else we need to know?:
N/A

Metadata

Metadata

Assignees

Labels

kind/bugCategorizes issue or PR as related to a bug.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions