You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
If my setup will have only one gateway, is it better to create separate envoy namepsace for it and store TLS secrets here or I can store this Gateway with TLS secrets inside envoy-gateway-system namespace?
Also by some reason I'm unable to join Slack community - it allows to join only if you have lyft or linuxfoundation email
The text was updated successfully, but these errors were encountered:
matrix-root
changed the title
Single-namespace RBAC and secure place for storing TLS-certificates and Gateway
Secure place for storing TLS-certificates and Gateway
Jun 28, 2024
matrix-root
changed the title
Secure place for storing TLS-certificates and Gateway
Most Secure place for storing TLS-certificates and Gateway
Jun 28, 2024
@matrix-root the TLS certs are usually configured by the platform owner or app owner, so I'd put it in a namespace that they own, and not the envoy-gateway-system namespace, access to this ns should be treated with more scrutiny
Description:
If my setup will have only one gateway, is it better to create separate
envoy
namepsace for it and store TLS secrets here or I can store this Gateway with TLS secrets insideenvoy-gateway-system
namespace?Also by some reason I'm unable to join Slack community - it allows to join only if you have lyft or linuxfoundation email
The text was updated successfully, but these errors were encountered: