GatewayHTTPListenerIsolation (and other features) are listed as both Standard and Extended

[candita]

What happened:
https://github.com/kubernetes-sigs/gateway-api/blob/main/pkg/features/gateway.go#L80-L84 shows it as Standard and https://github.com/kubernetes-sigs/gateway-api/blob/main/pkg/features/gateway.go#L103 shows it as extended.

What you expected to happen:
A feature should be either Standard or Extended so that we can test Standard conformance separately from extended conformance.

How to reproduce it (as minimally and precisely as possible):
n/a

Anything else we need to know?:
When conformance tests run, the feature shows up in both supported and unsupported stanzas. There are numerous places in the feature code where features exist as both standard and extended.

[candita]

/label area/conformance

[k8s-ci-robot]

@candita: The label(s) /label area/conformance cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, ci-short, ci-extended, ci-full. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/label area/conformance

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[candita]

/area conformance

[mlavacca]

This is not a bug. The concept of channel (standard/experimental) and feature type (core/extended) are orthogonal: The feature GatewayHTTPListenerIsolation is an extended feature related to the spec belonging to the standard channel.

I'm closing the issue. Feel free to re-open it if you deem it necessary.