Skip to content

Support BackendTLSPolicy SubjectAltNames #3152

@sjberman

Description

@sjberman
Collaborator

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

Activity

github-actions

github-actions commented on Mar 7, 2025

@github-actions
Contributor

This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 14 days.

removed
stalePull requests/issues with no activity
on Mar 11, 2025
added this to the v2.1.0 milestone on Mar 17, 2025
modified the milestones: v2.1.0, v2.2.0 on Jul 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/gateway/extendedRelates to all extended features of Gatewayarea/securityFor security best practicesenhancementNew feature or request

    Type

    No type

    Projects

    Status

    🆕 New

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @mpstefan@sjberman

        Issue actions

          Support BackendTLSPolicy SubjectAltNames · Issue #3152 · nginx/nginx-gateway-fabric