[EPIC] Add support for SSLConfig settings in K8S Gateway API

[DuncanDoyle]

Gloo Edge Product

Open Source

Gloo Gateway Version

1.18.2

Is your feature request related to a problem? Please describe.

The classic Gloo Edge API provides a SSLConfig proto that provides a number of configuration options that are often used by our users, in particular:

• oneWayTls
• alpnProtocols
• parameters (to set the supported cipher suites, min/max protocol versions, etc).

In our K8S Gateway API implementation we currently do not support these settings, which prevents some of our users that rely on these features to move to GW API.

Rather than tackling these individual features one by one, this epic aims to gather the requirements for the most used SSLConfig options so we can design this feature as a whole, rather than implement small individual pieces of it.

Note that there seem to be a number of K8S Gateway API issues that discuss some of these configuration options:

ALPN:

• GEP: TLS ALPN Routing kubernetes-sigs/gateway-api#1958

Cipher Suites:

• https://gateway-api.sigs.k8s.io/guides/tls/#extensions

Describe the solution you'd like

Support for the:

• oneWayTls
• alpnProtocols
• paramaters

options of the SSLConfig proto in our K8S Gateway API implementation.

Describe alternatives you've considered

n.a.

Additional Context

n.a.

Sub Issues:

• Supporting oneWayTls flag in Gloo Gateway (K8S Gateway API) to enforce one way TLS. #10169
• https://github.com/solo-io/solo-projects/issues/7505
• Add SSLConfig alpnProtocols support to Gloo Gateway's K8S Gateway API #10418