feat: rm byoc; only mention hybrid #179
Conversation
markphelps
commented
Jan 31, 2024
markphelps
commented
- rm mention of byoc
- refactor hybrid docs a bit
- replace hybrid image
|
|
||
| **Hybrid Cloud: The Best of Both Worlds** | ||
|
|
||
| - Our Hybrid Cloud solution offers a streamlined setup, ready-to-use management interface, and simplified user and integration management, ensuring a smooth transition and enhanced operational efficiency. | ||
|
|
||
| - Flipt Hybrid cloud handles user authentication and authorization, ensuring that your feature flags are secure and accessible only to the right people. |
There was a problem hiding this comment.
The authz part is making sure that users are routed to their correct instance?
There was a problem hiding this comment.
I think initially, but the goal would be to offer more than just instance level authz. Since we can apply policy decisions at the HTTP layer before forwarding.
images/managed/hybrid.png
Outdated
There was a problem hiding this comment.
Open question: Do we want to keep pushing the deploy Flipt in different locations to support multiple environements like this diagram suggests? Or do we want to name them something other than staging and production?
Im not sure either way if I am honest. The naming you have here is familiar and relatable.
There was a problem hiding this comment.
i think its the most natural way to run Flipt for large orgs in separate VPCs so to me it makes sense. But if we hear otherwise I'm up to change it
Co-authored-by: Yoofi Quansah <[email protected]>
Co-authored-by: George <[email protected]>
