Dynamo namespace based isolation #28
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
biswapanda
requested review from
athreesh,
grahamking,
ishandhanani,
nnshah1 and
ryanolson
nnshah1
reviewed
Aug 13, 2025
| @@ -0,0 +1,199 @@ | |||
| # Multi-tenancy support for DynamoGraphDeployment | |||
There was a problem hiding this comment.
Suggested change
| # Multi-tenancy support for DynamoGraphDeployment | |
| # Frontend Isolation in DynamoGraphDeployment |
There was a problem hiding this comment.
open to other thoughts here - but want to pull back from the notion of mult-tenancy and consider this more of isolation and reuse of nats / etcd for dynamo clusters.
we should break it into nats / etcd as part of the dynamo cloud instance?
So each k8s namespace has an operator and nats / etcd
every deployment within that share that nats and etcd
in order to deploy multiple isolated graphs within that deployment - we need hierarchical namspaces
I think we should motivate that last via customer requirement - is that needed? Likely yes -
biswapanda
changed the title
biswapanda
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.