Currently the HCO APIs include a stanza named featureGates with a few product options there:

  featureGates: 
    deployTektonTaskResources: false
    enableCommonBootImageImport: true
    withHostPassthroughCPU: false
    disableMDevConfiguration: false
    deployKubeSecondaryDNS: false
    nonRoot: true
    enableManagedTenantQuota: false
    deployVmConsoleProxy: false
    persistentReservation: false

but regardless of the name, being part of the actual API they are configuration options that should be handled as proper APIs over the various product versions.

On the other side FeatureGates by definition evolve and then disappear as the feature graduates.

Openshift has a well defined process around FGs:
https://github.com/openshift/enhancements/blob/master/dev-guide/featuresets.md

As part of this story we should clearly differentiate config options (that are going to remain in the product) from feature gates (that are going to disappear as the product matures) having a mechanism to handle FeatureGates in the future.

As part of this story we have to convert existing config options that are going to remain in the product.