Plan a Deployment

Mon, 01 Jan 0001 00:00:00 +0000

Layer5 Cloud starts with unsafe placeholder values for every secret and with localhost for every URL. Settle the decisions below first, so the install is a single helm install with a complete values file.

Decisions to make 🔗

Decision	What to settle	Where it is configured
Database	A PostgreSQL server that hosts three databases: `meshery`, `kratos`, and `hydra`.	`env.db`, `env.kratosdb`, `env.hydradb`, and the subchart `dsn` values
Hostname and TLS	One public hostname, a certificate for it, and the scheme (`https`).	`ingress.*`, `env.serverbaseurl`, `env.serverHost`, `env.proto`
Secrets	Replace every placeholder before first start. See Secrets to generate.	`env.`, `kratos.`, `hydra.*`
Identity providers	The Google and GitHub OAuth applications that act as the default sign-in providers. See Identity Services.	`env.providerOrg*`
Mail	A relay on a public address that offers STARTTLS (or implicit TLS on 465), and how identity mail leaves. See Mail.	`smtp.*`, Kratos courier values
First administrator	The Provider Admin account and the provider organization. See Provider initialization.	`env.initConfig`
Network paths	What must be reachable between components and from users. See Networking.	Ingress, network policy, egress rules
Observability	Where logs and traces go. See Monitoring.	`env.loglevel`, `env.otelConfig`

Database 🔗

Layer5 Cloud creates and migrates its own schema. The server applies migrations every time it starts, and exits if a migration fails, so give the database user the rights to create tables and the uuid-ossp extension in the public schema of the meshery database. Kratos and Hydra run their own migrations when the chart’s automigration setting is on, which is the default.

Planning on Layer5 Documentation

Plan a Deployment

Decisions to make 🔗

Database 🔗