Skip to content

Graduate otherNames feature gate from alpha to beta #8247

@fadecore

Description

@fadecore

Is your feature request related to a problem? Please describe.
We are using the feature behind the flag otherNames and would like it to be graduated to beta and anabled as default by cert-manager.
The graduation would help us a lot in adoption, because alpha feature-gates need dedicated discussions in enterprises and have a higher risk of deprecation.

Describe the solution you'd like
Don't know what is needed.

Describe alternatives you've considered
enable as feature-gate

Additional context
We are using cert-manager with the otherNames feature-gate together with our (custom) CA to transport an additional OID 1.3.6.1.5.5.7.1.34 for NFType, that is used to generate certifcates compliant to https://datatracker.ietf.org/doc/html/rfc9310
This is not the typical usecase for the feature like discussed in the original issue #6393 but helps us a lot, thanks to the flexible implementation.

Example:

  otherNames:
    # Should only supply oid of ut8 valued types
    - oid: 1.3.6.1.5.5.7.1.34 # Set RFC9310 compliant NFType string https://datatracker.ietf.org/doc/html/rfc9310#name-nftype-strings
      utf8Value: "SEPP"

/kind feature

Metadata

Metadata

Labels

kind/featureCategorizes issue or PR as related to a new feature.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions