sting cloud resources

Existing Kubernetes clusterIf you already have an existing cluster without an ingress controller, you can jump straight to the deploy command above to get going with the defaults. Please make sure that you have your local kubectl configured to talk to your cluster.

Having an existing NGINX Ingress Controller

The deploy command, by default, tries to create an NGINX ingress controller on your cluster. If you already have an existing controller, you can tell ZenML to not re-deploy it through the use of a config file. This file can be found in the Configuration File Templates towards the end of this guide. It offers a host of configuration options that you can leverage for advanced use cases.

Check if an ingress controller is running on your cluster by running the following command. You should see an entry in the output with the hostname populated.Copy# change the namespace to any other where 
# You might have the controller installed
kubectl get svc -n ingress-nginx

Set create_ingress_controller to false.

Supply your controller's hostname to the ingress_controller_hostname variable.Note: The address should not have a trailing /.

You can now 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.

Existing hosted SQL database

If you also already have a database that you would want to use with the deployment, you can choose to configure it with the use of the config file. Here, we will demonstrate setting the database.

Fill the fields below from the config file with values from your database.Copy# The username and password for the database.
database_username: 
database_password:

# The URL of the database to use for the ZenML server.
database_url:

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