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
When it comes to applications, security is up to them. But the k8s-router does allow you to have some level of security in that you need an API Key to access your deployments. Thankfully this is opt-in and not required but for those that do want it, we need a better solution. Right now the keys are static and created at the namespace level. It would be nice to give the deployment owner more control as to which key(s) to use.
While this is not to be confused with authentication as a service, we could eventually turn this into a lightweight, API Management feature supporting more than just simple keys.
The text was updated successfully, but these errors were encountered:
When it comes to applications, security is up to them. But the
k8s-router
does allow you to have some level of security in that you need an API Key to access your deployments. Thankfully this is opt-in and not required but for those that do want it, we need a better solution. Right now the keys are static and created at the namespace level. It would be nice to give the deployment owner more control as to which key(s) to use.While this is not to be confused with authentication as a service, we could eventually turn this into a lightweight, API Management feature supporting more than just simple keys.
The text was updated successfully, but these errors were encountered: