What's on this page


Getting Started

This section details how to install Stratoss™ Lifecycle Manager (LM) using Helm on an existing Kubernetes cluster. This will install the following Helm charts: helm-foundation - reference Helm Chart for deploying the third-party components required by Stratoss LM. lm-configurator - Helm Chart executing a Kubernetes job to create relevant schemas and other configuration required by Stratoss LM. lm-helm - Helm Chart for deploying the Stratoss LM Microservices Note : If following the IBM Installation Guide, please proceed to this section to skip the preparation of the environment and installation media, and continue with the configuration Access Configuration »

Access Configuration

Configuring Access to Stratoss™ Lifecycle Manager (LM) The installation of Stratoss LM includes an Ingress Controller which exposes the key services externally. This needs to be configured so that access to these services will be on the required hostnames and ports. If your environment already has an Ingress Controller available, then disable the one that comes with the LM installation. You can check the status of your ingress controller with: »


Configuring Sizing of Stratoss™ Lifecycle Manager (LM) The default install of LM makes use of the default settings, which will deploy the Standard flavour of LM. This includes: single instance of Foundation services execution of the LM configurator job to configure default settings single instance of Stratoss LM services, with all security features enabled Alternative Sizing Flavours The flavours directory included in the lm-helm-charts package contains helm values and other useful files for installing alternative recommended deployments of the Stratoss LM. »


The following guide explains how to pre-prepare the artifacts required by Stratoss™ Lifecycle Manager (LM) during installation so you may complete installation at a later date without internet access. Preparing Offline Install Helm Charts The Helm charts should have already been gathered and copied onto the installation machine. Docker Images Create a workspace mkdir lm-docker-images Identifying Images Below is a full list of the docker images used by the sub-charts in v2. »


Configuring Security in Lifecycle Manager The recommended installation of Lifecycle Manager is with security enabled. This will give the following benefits: HTTPS access to services Role-based Access Control to the Lifecycle Manager user interface Protected access to LM APIs Disabling Security The easiest way to disable security during installation is by including the No Security flavour No Security Flavour Directory: no-security This flavour disables LM security and is intended for development/testing purposes. »


Storage Class By default, any service requiring persistence is configured to use the default provisioner of your Kubernetes cluster. You can check your default with kubectl: kubectl get storageclass The default storage class will be shown with (default) alongside it’s name. If you have no default, you can mark an existing class as the default with: kubectl patch storageclass <your-class-name> -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}' The values provided with the Helm charts in LM configure specific storage classes which need overriding in order to use the system default. »

External LDAP

Configuring an External LDAP Server To use an LDAP Server other than the pre-configured OpenLDAP instance which comes as part of the LM installation, follow these steps. Disable Installation and Set Up of OpenLDAP To disable the installation and set up of OpenLDAP when using an existing LDAP, add the following to the custom Helm values file: openldap: enabled: false configurator: security: ldap: enabled: false Modify LDAP connection configuration Stratoss ™ Lifecycle Manager (LM) comes with configuration based on the directory structure which exists in the pre-configured install of OpenLDAP. »

Install LM

This section assumes you have followed the configuration steps and now have: a helm-foundation Helm chart an lm-configurator Helm chart an lm-helm - Helm chart a custom values YAML file Installing with Helm You can now install the various LM Helm charts in the order listed above, using the helm install command helm install <your-helm-chart> --name <your-release-name> --namespace <your-namespace> -f <your-custom-values-file> -f <your-additional-flavour-files> cicdhub-helm-chart - path to the Helm chart your-release-name - unique name used to identify this installation in Helm your-namespace - Kubernetes namespace to install into (leave out to use default). »