Skip to content

[feature] Transition to Multi-Tenant eVault architecture #389

@coodos

Description

@coodos

Description

Transition to Multi-Tenant architecture from individual Pods, More details described in https://izi.synology.me:792/oo/r/15dlpqdNej5iriqgUBISkqIToI9utFAq

Acceptance Criteria

  • TBD, map one user per PORT Use HTTP headers to seperate users

    Decided to move to X-ENAME header in each HTTP request instead, so it keeps the URI the same, and no need to add a path variable, but it does end up breaking the connectivity because adapter would need to be changed in order to use http header to talk to eVaults instead of IP + Port making an eVault at the end.

  • Move PVC out of eVaults so that it's an enviroment config issue on how many users are mapped to one DB instance

  • Make eVault software completely stateless

  • Add eName to metadata of a MetaEnvelope

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions