-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DOC-622 clean up Hybrid docs and add architecture diagram #26549
Conversation
Signed-off-by: nikki everett <[email protected]>
- No ingress is required from Dagster+ to user environments | ||
- Dagster+ doesn't have access to user code. Metadata about the code is fetched over constrained APIs. | ||
- The Dagster+ agent is [open source and auditable](https://github.com/dagster-io/dagster-cloud) | ||
Common security considerations in Dagster+ hybrid include: |
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.
Are these recommendations for the user to follow? If so, I'll move them to the index page for the hybrid section (which is basically the setup page).
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.
Yes they are
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.
The new diagram looks great
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Summary & Motivation
*Updates hybrid deployment index page to focus on setup and architecture page to focus on architecture
How I Tested These Changes
Local deployment.
Changelog