Different feature gates involve different teams. Though they all are defined in above repos, per https://github.com/openshift/api/pull/550/files#diff-a5a3801c705742637eeef3b8e7d76bb8R134 it is sig-network, therefore moving to Networking component accordingly (it requires Subcomponent not sure which one is OK)
verified this bug on 4.3.0-0.nightly-2019-12-29-173422 oc get featuregates -o yaml apiVersion: v1 items: - apiVersion: config.openshift.io/v1 kind: FeatureGate metadata: annotations: release.openshift.io/create-only: "true" creationTimestamp: "2019-12-30T08:10:58Z" generation: 2 name: cluster resourceVersion: "22532" selfLink: /apis/config.openshift.io/v1/featuregates/cluster uid: ba5dd10a-11fc-4354-8675-81e041cb4a7b spec: featureSet: LatencySensitive kind: List metadata: resourceVersion: "" selfLink: "" oc get svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE sctpserver ClusterIP 172.30.37.246 <none> 30100/SCTP 43s
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0062