-
Notifications
You must be signed in to change notification settings - Fork 561
Much better Pro docs #4263
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
Open
AlexejPenner
wants to merge
37
commits into
docs/pro-vs-oss
Choose a base branch
from
docs/better-pro-docs
base: docs/pro-vs-oss
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Much better Pro docs #4263
Changes from all commits
Commits
Show all changes
37 commits
Select commit
Hold shift + click to select a range
f4e15b8
Initial commit
AlexejPenner 2946cc1
Fixed formatting
AlexejPenner 23a0759
Pruned away hallucinations
AlexejPenner c7e7517
Some more in depth docs
AlexejPenner 299fed1
Adjusted time to production
AlexejPenner 3788483
Adjusted some wording
AlexejPenner e7b164b
Linking across new files properly
AlexejPenner 27a608f
Adjusted cards
AlexejPenner b67b31b
Some streamlining
AlexejPenner 53fd01f
Adjusted naming self-hosted
AlexejPenner bb5cfc2
Slight rewording in table
AlexejPenner 8d705e9
Slight rewording in table
AlexejPenner d70df0b
Edited all the overview pages
AlexejPenner b33baea
Fixed renaming leftovers
AlexejPenner 700a65c
Update docs/book/getting-started/zenml-pro/saas-deployment.md
AlexejPenner 21eb029
Implemented some pr comments
AlexejPenner 21861c8
Merge branch 'docs/better-pro-docs' of github.com:zenml-io/zenml into…
AlexejPenner 56fe203
Removed diagrams from detail tabs
AlexejPenner 053f589
Specify Pro server
AlexejPenner 0be4fc5
Added image
AlexejPenner 0a6bdfa
Optimised images with calibre/image-actions
github-actions[bot] 02e53c8
Applied some more reviews
AlexejPenner 2d32d12
Add actual docker image URI
AlexejPenner 187b488
Applied Alex's review
AlexejPenner a36e8ea
Merge branch 'docs/pro-vs-oss' into docs/better-pro-docs
AlexejPenner ee3ea6a
Update docs/book/getting-started/zenml-pro/self-hosted.md
AlexejPenner dadc63b
Applied stefans review comments part 1
AlexejPenner 7c0db33
Merge branch 'docs/better-pro-docs' of github.com:zenml-io/zenml into…
AlexejPenner cb5d327
Additional PR comments applied
AlexejPenner fb79faa
Update docs/book/getting-started/zenml-pro/hybrid-deployment.md
AlexejPenner df1a223
Update docs/book/getting-started/zenml-pro/hybrid-deployment-helm.md
AlexejPenner d492c68
Further adjustments and improvments
AlexejPenner 7e451a2
Merge branch 'docs/better-pro-docs' of github.com:zenml-io/zenml into…
AlexejPenner d1f12fd
Further consolidation
AlexejPenner 9a839ac
Last small hint
AlexejPenner 7deeb8b
New servicces section
AlexejPenner 5f10e55
Resorted Services
AlexejPenner File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Binary file added
BIN
+257 KB
docs/book/getting-started/zenml-pro/.gitbook/assets/pro-workload-managers.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or 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 hidden or 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,156 @@ | ||
| --- | ||
| description: Deep dive into the ZenML Control Plane - responsibilities, permissions, and network requirements. | ||
| icon: shield-halved | ||
| --- | ||
|
|
||
| # Control Plane | ||
|
|
||
| The **ZenML Control Plane** is the organization-level management layer in ZenML Pro. It sits above individual workspaces and provides centralized authentication, authorization, and administrative functions. | ||
|
|
||
| ## Responsibilities | ||
|
|
||
| The Control Plane handles organization-wide concerns that span multiple workspaces: | ||
|
|
||
| ### Authentication & Identity | ||
|
|
||
| - **User authentication**: SSO integration, login flows | ||
| - **Identity federation**: SAML, OIDC, and social login providers | ||
| - **API key management**: Personal access tokens and service account credentials | ||
|
|
||
| ### Authorization & RBAC | ||
|
|
||
| - **Role management**: Define and assign org level roles (Admin, Editor, Viewer, etc.) | ||
| - **Permission enforcement**: Control who can access what across workspaces | ||
| - **Team management**: Group users into teams with shared permissions | ||
|
|
||
| ### Organization Management | ||
|
|
||
| - **Workspace provisioning**: Create, configure, and delete workspaces | ||
| - **User management**: Invite users, manage memberships, handle offboarding | ||
|
|
||
|
|
||
| ### Workspace Coordination | ||
|
|
||
| - **Workspace registry**: Maintains list of all workspaces in the organization | ||
| - **Health monitoring**: Tracks workspace status (Hybrid/Self-hosted) | ||
| - **Version management**: Coordinates workspace upgrades (SaaS only) | ||
|
|
||
| ## Where It Runs | ||
|
|
||
| | Deployment | Control Plane Location | | ||
| |------------|------------------------| | ||
| | **SaaS** | ZenML infrastructure (fully managed) | | ||
| | **Hybrid** | ZenML infrastructure (fully managed) | | ||
| | **Self-hosted** | Your infrastructure (you manage) | | ||
|
|
||
| ## Required Permissions | ||
|
|
||
| ### For Self-hosted Deployments | ||
|
|
||
| When running your own Control Plane, you need: | ||
|
|
||
| **Database permissions:** | ||
| - Same as Workspace Server (full CRUD on control plane database) | ||
| - Separate database recommended for isolation | ||
|
|
||
| **Identity provider integration:** | ||
| - OAuth2/OIDC client credentials | ||
| - SAML metadata exchange (if using SAML) | ||
|
|
||
| ## Network Requirements | ||
|
|
||
| ### Ingress (Incoming Traffic) | ||
|
|
||
| The Control Plane must accept connections from: | ||
|
|
||
| | Source | Port | Protocol | Purpose | | ||
| |--------|------|----------|---------| | ||
| | User browsers | 443 | HTTPS | Dashboard login, UI access | | ||
| | ZenML SDK clients | 443 | HTTPS | Authentication, token exchange | | ||
| | ZenML Workspace | 443 | HTTPS | Workspace registration, heartbeats | | ||
| | Identity providers | 443 | HTTPS | SSO callbacks | | ||
|
|
||
| ### Egress (Outgoing Traffic) | ||
|
|
||
| The Control Plane needs to reach: | ||
|
|
||
| | Destination | Port | Protocol | Purpose | | ||
| |-------------|------|----------|---------| | ||
| | Identity providers | 443 | HTTPS | SSO authentication flows | | ||
| | Database | 3306/5432 | TCP | Persistent storage | | ||
|
|
||
| ### Network Diagram | ||
|
|
||
| ``` | ||
| ┌─────────────────────────────────────┐ | ||
| │ Control Plane │ | ||
| │ (cloud.zenml.io or yours) │ | ||
| └──────────────┬──────────────────────┘ | ||
| │ | ||
| ┌────────────────────────┼────────────────────────┐ | ||
| │ │ │ | ||
| ▼ ▼ ▼ | ||
| ┌───────────────┐ ┌───────────────┐ ┌───────────────┐ | ||
| │ Workspace A │ │ Workspace B │ │ Workspace C │ | ||
| │ (Your Infra) │ │ (Your Infra) │ │ (Your Infra) │ | ||
| └───────────────┘ └───────────────┘ └───────────────┘ | ||
| ``` | ||
|
|
||
| ## Authentication Flows | ||
|
|
||
| ### User Login (Browser) | ||
|
|
||
| ``` | ||
| User Browser → Control Plane → Identity Provider → Control Plane → UI | ||
| │ | ||
| └── Issues session token | ||
| ``` | ||
|
|
||
| ### SDK Authentication | ||
|
|
||
| ``` | ||
| SDK → Control Plane → Validates credentials → Returns API token | ||
| │ | ||
| └── Token used for Workspace Server requests | ||
| ``` | ||
|
|
||
| ### Workspace Registration (Hybrid) | ||
|
|
||
| ``` | ||
| Workspace Server → Control Plane → Validates enrollment key → Registers workspace | ||
|
|
||
| ``` | ||
|
|
||
| ### Resource Recommendations | ||
|
|
||
| | Deployment Size | CPU | Memory | Notes | | ||
| |-----------------|-----|--------|-------| | ||
| | Small (< 50 users) | xxx | xxx | Single instance sufficient | | ||
| | Medium (50-500 users) | xxx | xxx | Consider high-availability setup | | ||
| | Large (> 500 users) | xxx | xxx | Multi-replica with load balancing | | ||
|
|
||
| ## Security Considerations | ||
|
|
||
| ### Data Handled by Control Plane | ||
|
|
||
| | Data Type | Sensitivity | Storage | | ||
| |-----------|-------------|---------| | ||
| | User credentials | High | Managed through IDP | | ||
| | API tokens | High | Encrypted at rest | | ||
| | Organization settings | Medium | Control Plane database | | ||
| | Audit logs | Medium | Control Plane database | | ||
| | Workspace metadata | Low | Control Plane database | | ||
|
|
||
| {% hint style="success" %} | ||
| The Control Plane **never** has access to your ML data, artifacts, or pipeline code. It only handles authentication and organizational metadata. | ||
| {% endhint %} | ||
|
|
||
| ## Related Documentation | ||
|
|
||
| - [Workspace Server](workspace-server.md) - Pipeline metadata and execution | ||
| - [Workload Managers](workload-managers.md) - Running pipelines from the UI | ||
| - [Roles & Permissions](roles.md) - Detailed RBAC configuration | ||
| - [Service Accounts](service-accounts.md) - Programmatic access setup | ||
|
|
||
| <figure><img src="https://static.scarf.sh/a.png?x-pxid=f0b4f458-0a54-4fcd-aa95-d5ee424815bc" alt="ZenML Scarf"><figcaption></figcaption></figure> | ||
|
|
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.