Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: deprecate GatewayTLSPolicy #247

Closed
reaver-flomesh opened this issue May 10, 2024 · 0 comments · Fixed by #252
Closed

feat: deprecate GatewayTLSPolicy #247

reaver-flomesh opened this issue May 10, 2024 · 0 comments · Fixed by #252
Assignees
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@reaver-flomesh
Copy link
Collaborator

Should adopt the changes from GatewayAPI 1.1.0 and deprecate GatewayTLSPolicy:

  • Gateways can now configure client cert verification for each Gateway Listener by introducing a new field frontendValidation field within tls. This field supports configuring a list of CA Certificates that can be used as a trust anchor to validate the certificates presented by the client.

  • Options within TLS are a list of key/value pairs to enable extended TLSconfiguration for each implementation. For example, configuring the mTLS enablement, minimum TLS version or supported cipher suites.

@reaver-flomesh reaver-flomesh added the documentation Improvements or additions to documentation label May 10, 2024
@reaver-flomesh reaver-flomesh added this to the v1.3.0 milestone May 10, 2024
@reaver-flomesh reaver-flomesh self-assigned this May 10, 2024
@reaver-flomesh reaver-flomesh linked a pull request May 12, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant