-
Notifications
You must be signed in to change notification settings - Fork 40
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #173 from corkrean/corkrean_dedicated_updates
isolation doc and dedicated configuration guide
- Loading branch information
Showing
12 changed files
with
72 additions
and
3 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,56 @@ | ||
# SpiceDB Dedicated Configuration | ||
|
||
This guide provides information about the configuration options available to you when deploying a SpiceDB Dedicated Permissions System. | ||
|
||
## Configuration Options | ||
|
||
### Permissions System Type | ||
|
||
<img src={require("/img/ps-type.png").default} alt="permissions system type" /> | ||
|
||
Please select the choice (Production or Development) that is appropriate for the Permissions System you are deploying. This choice will not effect the performance or security of your Permissions System, but may impact your Permissions System in the future, so please choose appropriately. | ||
|
||
### Datastore | ||
|
||
<img src={require("/img/datastore-config-v2.png").default} alt="datastore configuration" /> | ||
|
||
Your SpiceDB Dedicated environment can be provisioned with multiple isolated [datastores](/spicedb/selecting-a-datastore.md). If you have more than one, choose the datastore that is appropriate for the Permissions System you are deploying. | ||
|
||
### Update Channel | ||
|
||
<img src={require("/img/channels-config.png").default} alt="channels config" /> | ||
|
||
SpiceDB Dedicated has two update channels: `rapid` and `regular` . You can select the update channel when you launch the Permissions System or in the settings page after you’ve launched it. | ||
|
||
`rapid` - gets every release that is not a release candidate. | ||
|
||
`regular` - trails behind `rapid` by at least one release. | ||
|
||
After you’ve deployed your Permissions System, you can choose to keep up to date with a channel automatically, or you can “pin” to a version by un-checking the automatic updates box. If you uncheck the automatic release box, you’ll still be able to update, but will have to pick the next version manually. | ||
|
||
<img src={require("/img/update_box_v2.png").default} alt="update box" /> | ||
|
||
### Rollout Strategy | ||
|
||
<img src={require("/img/rollout-strategy.png").default} alt="rollout strategy" /> | ||
|
||
There are two rollout strategies: `rolling update` and `immediate`. | ||
|
||
- `rolling update` is a zero downtime strategy for upgrading to a new version. This is recommended for prod Permissions Systems. | ||
- `immediate` involves downtime, but is faster than `rolling update`. | ||
|
||
### Define Cluster(s) | ||
|
||
<img src={require("/img/define-clusters-v2.png").default} alt="define clusters" /> | ||
|
||
#### Single region deployment | ||
|
||
If you are deploying a single region Permissions System, define a single cluster. | ||
|
||
#### Multi-region deployment | ||
|
||
Define a cluster for every region you want to deploy into. | ||
|
||
#### Cluster Class | ||
|
||
For production clusters, we recommend selecting the Cluster Class with the largest number of replicas and processing units. For non-production clusters, you can select whatever Cluster Class is appropriate for your workload. If you have questions about your overall utilization or would like to provision a custom Cluster Class, please [reach out to your AuthZed account team](https://authzed.com/call). |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
# SpiceDB Dedicated Isolation | ||
|
||
SpiceDB Dedicated isolates your workloads from other customers. Cloud accounts, compute resources, databases, and networking are all dedicated to you. | ||
|
||
Additionally, SpiceDB Dedicated allows you to deploy multiple isolated Permissions Systems into a single SpiceDB Dedicated environment. Each Permissions System has it’s own schema and set of relationships. Also, these Permissions Systems impose memory and CPU limits so one Permissions System can’t crowd out another Permissions System. | ||
|
||
By default, API tokens are scoped to a particular Permissions System. [Fine Grained Access Management (FGAM)](/spicedb-dedicated/fgam.md) can take this further by restricting API tokens to specified APIs, object types, or object IDs. | ||
|
||
The below diagram gives an overview of the SpiceDB Dedicated isolation model. | ||
|
||
<img src={require("/img/dedicated_isolation_v3.png").default} alt="dedicated isolation model" /> |
This file contains 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
This file contains 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
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
6d63118
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Successfully deployed to the following URLs:
docs – ./
docs.authzed.com
docs-authzed.vercel.app
docs-git-main-authzed.vercel.app