 use for the database connection.
database_ssl_ca:# The path to the client SSL certificate to use for the database connection.
database_ssl_cert:

# The path to the client SSL key to use for the database connection.
database_ssl_key:

# Whether to verify the database server SSL certificate.
database_ssl_verify_server_cert:

Run the deploy command and pass the config file above to it.Copyzenml deploy --config=/PATH/TO/FILENote To be able to run the deploy command, you should have your cloud provider's CLI configured locally with permissions to create resources like MySQL databases and networks.

Configuration file templates

Base configuration file

Below is the general structure of a config file. Use this as a base and then add any cloud-specific parameters from the sections below.

# Name of the server deployment.

name:

# The server provider type, one of aws, gcp or azure.

provider:

# The path to the kubectl config file to use for deployment.

kubectl_config_path:

# The Kubernetes namespace to deploy the ZenML server to.

namespace: zenmlserver

# The path to the ZenML server helm chart to use for deployment.

helm_chart:

# The repository and tag to use for the ZenML server Docker image.

zenmlserver_image_repo: zenmldocker/zenml

zenmlserver_image_tag: latest

# Whether to deploy an nginx ingress controller as part of the deployment.

create_ingress_controller: true

# Whether to use TLS for the ingress.

ingress_tls: true

# Whether to generate self-signed TLS certificates for the ingress.

ingress_tls_generate_certs: true

# The name of the Kubernetes secret to use for the ingress.

ingress_tls_secret_name: zenml-tls-certs

# The ingress controller's IP address. The ZenML server will be exposed on a subdomain of this IP. For AWS, if you have a hostname instead, use the following command to get the IP address: `dig +short <hostname>`.

ingress_controller_ip:

# Whether to create a SQL database service as part of the recipe.

deploy_db: true

# The username and password for the database.