Welcome to part 3 of a multi-part series where I will walk through the setup and configuration of Rancher.
In the previous posts, I walked through the installation of Rancher, deploying the server and 3 hosts that can run dockerized workloads. I then deployed a Jenkins Stack and a Load Balancer from the default catalogs.
In this post I will show you how to create a private catalog and modify the Load Balancer Stack to account for a new service.
Rancher has the ability add user defined catalogs to the system. These are implemented as git repositories and contain all of the metadata necessary to define and instantiate any number of services.
As an example, I decided to create a catalog which offered a Tiny Tiny RSS service. I currently run ttrss on one of my servers so this would be a good test.
The documentation from Rancher Labs is very good and details the steps very well but I always find a real world example to be much better so here's a link to my catalog. The structure is pretty simple: Under the 'templates' directory, there is a directory per service (for example, I created a 'templates/ttrss' directory). Within that service directory, you place all of the metadata that is needed by Rancher.
Take a look at my catalog and it should be self explanatory
In order to add a Catalog to Rancher, you'll need three bits of information:
git clone. I used a public repository to make it really simple.
Go to the "Admin"->"Settings" page and add your catalog.
The entries should show up almost immediately after you go to the "Catalog" section of the UI
Deploying a service from a Private Catalog is EXACTLY like using one of the default catalogs. Simply click on the service you want to deploy, fill out the form and press "Launch". In the screenshot below, you can see how the different files in the catalog provide information for the user.