CS Launch Bitnami

Introduction

We used to support an encourage users to use the Bitnami helm charts for installing CS Launch Apps. However, they have moved to a paid service so it is no longer feasible for us to use them. Currently, we suggest to use either:

• Manual deployment of Docker official images: https://hub.docker.com/u/library
  • Example deployment: CS Launch MariaDB
• Groundhog2k helm charts (based on the Docker official images): https://github.com/groundhog2k/helm-charts
  • Example deployment: HowTo:CS_Launch#Launching_a_Database_Using_Helm

Migration Strategies

If you have an existing Bitnami deployment that you need to keep active, then here are some strategies to keep your deployment working.

Legacy Bitnami

The Bitnami crew are moving their images to a legacy repository. Support for this is likely to be short term, and updates are unlikely.

• You should be able to immediately switch your bitnami... images definitions to bitnamilegacy... to continue working

Full Replacement

Probably the best solution is to completely replace your Bitnami deployment to either a manual deployment of the Official Docker image or groundhog2k chart deployment. This would involve the following steps:

• Backup all current data and configurations
• Delete Bitnami deployment
• Deploy new instance using an currently supported method
• Import the backup data

In-Place Replacement

This method may require more work and intimate knowledge of how the deployment works. The idea is to replace the existing Bitnami docker image with an official docker image that is maintained. Some things to consider when trying this method:

• Make sure to make a backup of all data and configurations before attempting
• You will likely have to re-map existing configurations and secrets
• Data mounts might be different between the two images
• Make sure the application version is close to the same
• Future updates will have to be done manually instead of through the helm chart

Detailed Migration

We might provide more details instructions for popular deployments such as MariaDB, if needed.

Instructions Archive

Here is a copy of the old instructions using Bitnami for archive purposes. These instructions will no longer be supported.

Kubernetes supports Helm charts to automate deployment of software. There are existing Helm charts for many popular software projects, such as databases. Using a Helm chart can make setting up and updating complex software much easier. This guide will walk you through deploying MariaDB using a Helm chart from Bitnami.

• Navigate to your Cluster Dashboard
• Click on Apps from the menu on the left
• Click on Charts underneath Apps
• We need to find the MariaDB chart
  • Make sure to select Bitnami in the first drop down list
  • Select Database from the catagories drop down list
  • Click on the MariaDB tile
• Click on the Install button
• Select the namespace from the drop down list where you want the database deployed to
• Fill in Name with mariadb or a unique hostname you want to give your database
• Click on the Next button
• You will be presented with a long list of options and their default values in yaml format
• For our example, change the following options:

auth:
  database: 'test-db'
  username: 'test'
  password: 'Insecure'
primary:
  persistence:
    size: '1Gi'

• Click on the Install button
• It will take a minute or two for the deployment to complete. The site will give you a window to watch the progress, and report any errors that might occur.
• You should now have a running database, but no real way to access it yet
• Other pods in the same namespace will be able to connect to this database using the hostname mariadb