Date: Thu, 28 Mar 2024 07:54:48 -0600 (MDT) Message-ID: <122990757.2451.1711634088253@confluence-external-wiki> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2450_1759387681.1711634088253" ------=_Part_2450_1759387681.1711634088253 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This type of deployment can be used for proof-of-co= ncept, development or production: tools such as failover and horizonta= l scaling can be used with this environment, but it does not contain a reve= rse proxy or load balancer for sticky sessions.
For production deployments, we highly recommend i= nstalling one of these tools (see our other examples for how to deploy Yell= owfin on Kubernetes with Traefik; if you use a different tool or if yo= u wish to deploy Yellowfin without these tools, you= 're welcome to use these wiki pages as a guide, replacing Traefik informati= on 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 o= f 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.
Deployment |
Image= |
Description |
---|---|---|
Yellowfin s= andbox |
All-In-One<= /span> |
A self-cont= ained instance of Yellowfin. This is the simplest type of deployment. All c= ontent will be lost when the container is destroyed. |
Yellowfin s= ingle instance |
App-Only |
A single in= stance with a separate database, so data stored in the database will not be= lost when the container is destroyed. |
Yellowfin m= ultiple discrete instances |
App-Only |
Multiple in= stances 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 c= luster |
App-Only |
Multiple in= stances sharing a single database to form a Yellowfin c= luster. This could be used to stage a clustered environment durin= g a proof of concept. |
The page is part of the Install in a Container topic contains the following pages, split = by Docker and Kubernetes:
This page is part of the Install And Deploy Yellowfin = section of the wiki, which has these topics: