Commit Graph

3 Commits (a67d19317bc779b231f9311c28e82589704b3541)

Author SHA1 Message Date
Michael Bridgen a67d19317b
Explain authorisation model and mechanisms
The multi-tenancy implementations described rely on impersonation and
remote apply; to make this RFC stand by itself, those need to be
explained, along with the authorisation model (how Flux "decides" what
it's allowed to do).

This commit adds a summary of the authorisation model, impersonation,
and remote apply, and rejigs the headings a little to make space.

Signed-off-by: Michael Bridgen <michael@weave.works>
3 years ago
Stefan Prodan dc7cb189fc
Incorporate Michael's suggestions
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
3 years ago
Stefan Prodan d23d87ac94
Define Flux tenancy models
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
3 years ago