-
Notifications
You must be signed in to change notification settings - Fork 140
Closed as not planned
Labels
area/gateway/extendedRelates to all extended features of GatewayRelates to all extended features of Gatewayarea/securityFor security best practicesFor security best practicesbacklogCurrently unprioritized work. May change with user feedback or as the product progresses.Currently unprioritized work. May change with user feedback or as the product progresses.enhancementNew feature or requestNew feature or requestrefinedRequirements are refined and the issue is ready to be implemented.Requirements are refined and the issue is ready to be implemented.size/mediumEstimated to be completed within a weekEstimated to be completed within a week
Description
As an NGF user,
I want to specify Subject Alternative (SAN) names for my backends,
So that I can allow multiple alternative names to be present in the backend certificate.
Note: this may not actually be possible with nginx to support a list of SANs. See kubernetes-sigs/gateway-api#3591 which is changing this field to extended for this reason.
We still may want to investigate.
Acceptance
- Support the SubjectAltNames field in the BackendTLSPolicy
(Note: We may be able to only support a single subjectAltName, and this may be ok)
Note:
Metadata
Metadata
Assignees
Labels
area/gateway/extendedRelates to all extended features of GatewayRelates to all extended features of Gatewayarea/securityFor security best practicesFor security best practicesbacklogCurrently unprioritized work. May change with user feedback or as the product progresses.Currently unprioritized work. May change with user feedback or as the product progresses.enhancementNew feature or requestNew feature or requestrefinedRequirements are refined and the issue is ready to be implemented.Requirements are refined and the issue is ready to be implemented.size/mediumEstimated to be completed within a weekEstimated to be completed within a week
Type
Projects
Status
✅ Done