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
In some cases it might be nice to still have the separation of application in namespaces but still want to use the same tenant in the cloud aka AWS account or Azure resource group.
Today this isn't possible.
This solution isn't ideal from a security point of view since if one application gets hacked within this tenant probably all infrastructure under that tenant will bet hacked.
But as always it's a pros and cons thing. Less admin vs less hard barriers.
DoD: provide the simplest possible solution on how me as an admin can define the same tenant to be created in multiple namespaces without creating a new tenant.
The text was updated successfully, but these errors were encountered:
In some cases it might be nice to still have the separation of application in namespaces but still want to use the same tenant in the cloud aka AWS account or Azure resource group.
Today this isn't possible.
This solution isn't ideal from a security point of view since if one application gets hacked within this tenant probably all infrastructure under that tenant will bet hacked.
But as always it's a pros and cons thing. Less admin vs less hard barriers.
DoD: provide the simplest possible solution on how me as an admin can define the same tenant to be created in multiple namespaces without creating a new tenant.
The text was updated successfully, but these errors were encountered: