flux2

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>	4 years ago
Stefan Prodan	dc7cb189fc	Incorporate Michael's suggestions Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>	4 years ago
Stefan Prodan	d23d87ac94	Define Flux tenancy models Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>	4 years ago
Stefan Prodan	2c3cb1a664	Add template to RFC-0000 Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>	4 years ago
Stefan Prodan	99a0c47277	Add RFC process Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>	4 years ago
Stefan Prodan	c5b2c6709a	Add status, creation and last update date fields to RFC template Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>	4 years ago
Stefan Prodan	8354ac937c	Introduce the Flux RFC template The RFC template is heavily inspired by Rust RFCs and Kubernetes KEPs. Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>	4 years ago