mirror of
https://github.com/zitadel/zitadel.git
synced 2025-01-12 08:03:41 +00:00
docs(trainings): onboarding project (#4128)
* init * Apply suggestions from Florian Co-authored-by: Florian Forster <florian@caos.ch> Co-authored-by: Florian Forster <florian@caos.ch>
This commit is contained in:
parent
84c748581c
commit
7ff419779a
@ -10,7 +10,7 @@ Training should be held as block-sessions with the relevant staff from your orga
|
||||
|
||||
You receive professional onboarding support from our engineers, who help you to setup and configure ZITADEL on your infrastructure.
|
||||
|
||||
Effort required during depends on the complexity of your infrastructure and the overall setup. With a Multi-Zone Setup (excl. Multi-Region). Typically support during this phase requires around 10-25h over 2 weeks. Actual effort is based on time and material.
|
||||
[More information](project)
|
||||
|
||||
## Application Support Trainings
|
||||
|
||||
|
35
docs/docs/guides/trainings/project.md
Normal file
35
docs/docs/guides/trainings/project.md
Normal file
@ -0,0 +1,35 @@
|
||||
---
|
||||
title: Onboarding Project
|
||||
---
|
||||
|
||||
Effort required during depends on the complexity of your infrastructure and the overall setup. With a Multi-Zone Setup (excl. Multi-Region), support during this phase requires around 10-25h over 2 weeks. Actual effort is based on time and material.
|
||||
|
||||
Scope of the project is agreed on individual basis.
|
||||
|
||||
## In Scope
|
||||
|
||||
- Check prerequisites and architecture
|
||||
- Troubleshoot installation and configuration of ZITADEL
|
||||
- Troubleshoot and configuration connectivity to the database
|
||||
- Functional testing of the ZITADEL instance
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- Running multiple ZITADEL instances on the same cluster
|
||||
- Integration into internal monitoring and alerting
|
||||
- Multi-cluster architecture deployments
|
||||
- DNS, Network and Firewall configuration
|
||||
- Customer-specific Kubernetes configuration needs
|
||||
- Changes for specific environments
|
||||
- Performance testing
|
||||
- Production deployment
|
||||
- Application-side coding, configuration, or tuning
|
||||
- Changes or configuration on assets used in ZITADEL
|
||||
- Setting up or maintaining backup storage
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- Running Kubernetes with possibility to deploy to namespaces
|
||||
- Inbound and outbound HTTP/2 traffic possible
|
||||
- For being able to send SMS, we need a Twilio sender name, SID and an auth token
|
||||
- ZITADEL also needs to connect to an email relay of your choice. We need the SMTP host, user and app key as well as the ZITADEL emails sender address and name.
|
@ -145,7 +145,8 @@ module.exports = {
|
||||
items: [
|
||||
"guides/trainings/introduction",
|
||||
"guides/trainings/application",
|
||||
"guides/trainings/recurring"
|
||||
"guides/trainings/recurring",
|
||||
"guides/trainings/project",
|
||||
],
|
||||
},
|
||||
],
|
||||
|
Loading…
x
Reference in New Issue
Block a user