Like what you see? Have a play with our trial version.


This type of deployment can be used for proof-of-concept, development or production: tools such as failover and horizontal scaling can be used with this environment, but it does not contain a reverse proxy or load balancer for sticky sessions.  

For production deployments, we highly recommend installing one of these tools (see our other examples for how to deploy Yellowfin on Kubernetes with Traefik; if you use a different tool or if you wish to deploy Yellowfin without these tools,  you're welcome to use these wiki pages as a guide, replacing Traefik information with your own toolset).

However, if you prefer to deploy Yellowfin on Kubernetes without a load balancer or reverse proxy, you can follow the steps in this section of the wiki.

Single Yellowfin instance deployments don't require load balancing nor a reverse proxy, as they are already stand-alone.

Yellowfin cluster deployments require a load balancer or a reverse proxy so that sticky sessions are available.

Choose your preferred deployment from the table below, then follow the instructions.  




Yellowfin sandbox 


A self-contained instance of Yellowfin. This is the simplest type of deployment. All content will be lost when the container is destroyed. 

Yellowfin single instance 


A single instance with a separate database, so data stored in the database will not be lost when the container is destroyed. 

Yellowfin multiple discrete instances 


Multiple instances each with their own dedicated database. This could be used to stage a development environment and a production environment during a proof of concept. 

Yellowfin cluster 


Multiple instances sharing a single database to form a Yellowfin cluster. This could be used to stage a clustered environment during a proof of concept. 

Section navigation

This page is part of the Install And Deploy Yellowfin section of the wiki, which has these topics:

  • No labels