This topic provides automation steps for setting up an online, single-node Swimlane installation on embedded clusters.

Installation Preparation and Customization

System Requirements for an Embedded Cluster Install

 to confirm your system's compliance. The Swimlane Platform Installer (SPI) performs several checks in the initial phases of the installation to ensure the underlying host is compatible with the application. To bypass any applicable checks, an installer patch YAML file can be applied at installation time to account for several of these settings. Refer to 

apiVersion: "cluster.kurl.sh/v1beta1"
kind: "Installer"
metadata:
  name: "patch"
spec:
  kubernetes:
    HACluster: true
    loadBalancerAddress: "<Load Balancer FQDN or IP>:6443"
  firewalldConfig:
    disableFirewalld: true
  selinuxConfig:
    disableSelinux: true

Once you've accounted for any customizations and system checks, install an embedded cluster by running the following command:

curl -sSl https://get.swimlane.io/install | bash -s installer-spec-file=<Path to Patch File>.yaml

After the embedded Kubernetes cluster has been installed, install Swimlane with the following command:

kubectl kots install swimlane-platform \ 
  --namespace default \ 
  --shared-password <SPI Admin Console Password> \ 
  --license-file <SPI License File>.yaml \ 
  --port-forward=false \ 
  --config-values <SPI Config File>.yaml

 file is a YAML-formatted file that outlines the specifications of a Swimlane deployment. You can get the .yaml file from a previously configured installation of SPI or by creating a new file manually.

To obtain a file from a previously configured SPI install, run the following command from a system with access to the Kubernetes API and the SPI Kubectl Add-on installed:

kubectl kots download swimlane-platform -n <namespace>

This command downloads a copy of the entire SPI deployment specifications to a local folder named 

./swimlane-platform/upstream/userdata/config.yaml

To create the file manually, review the configurable options available in the 

Here is a basic version of the config file that you can use for an initial single-node configuration:

apiVersion: kots.io/v1beta1
kind: ConfigValues
metadata:
  creationTimestamp: null
  name: swimlane
spec:
  values:
    is_ha:
      value: "0"
    mongo_admin_user_password:
      value: <Base64 encoded string>
    mongo_admin_user_password_confirm:
      value: <Base64 encoded string>
    mongo_swimlane_user_password:
      value: <Base64 encoded string>
    mongo_swimlane_user_password_confirm:
      value: <Base64 encoded string>
    swimlane_database_encrypt_key:
      value: <Base64 encoded string>
    swimlane_database_encrypt_key_confirm:
      value: <Base64 encoded string>
    swimlane_enable_ingress:
      value: "1"
    swimlane_hostname:
      value: <Swimlane Hostname>

It takes a few minutes for Swimlane to initialize all of the required components. However, automation can effectively 'wait' for a ready state by waiting for a ready status from different parts of the deployment. There are multiple ways to accomplish this wait period, the following code block is just one example:

kubectl wait -l statefulset.kubernetes.io/pod-name=swimlane-sw-mongo-0 --for=condition=ready pod --namespace <Swimlane Namspace> --timeout=240s
export SW_API=$(kubectl get po -n <NameSpace> --no-headers -o custom-columns=":metadata.name" | grep -i api)  
kubectl wait --for=condition=ready pod $SW_API -n <NameSpace> --timeout=240s    

Next, continue with the Swimlane installation by creating the first administrative user.

Using your Swimlane license .lic file, first generate the necessary license block for the api call with a curl command:

curl -kLv -X POST https://<Swimlane URL>/api/settings/license/upload -H 'Content-Type: multipart/form-data' -F file=@<Swimlane License File>.lic

Then, to create the initial administrative user, insert the returned JSON into the following curl command:

curl -kLv -X POST https://<Swimlane URL>/api/settings/install \
  --header "Content-Type: application/json" \
  -d '{"mailSettings":{},
       "password":"<Admin Password>","confirmPassword":"<Admin Password>",
       "databaseEncryptionKey":"",
       "swimlaneUrl":"https://<Swimlane URL>",
       "license" :<Generated JSON Data From Previous Step>,
       "adminUserName":"<Admin Username>",
       "adminEmail":"<Admin Email>"}'

Automate an Online Embedded Installation

Automate an Offline Embedded Installation

Embedded Cluster SPI Config File

Automate Installation

test12

sdfdssdfsdfsdfsdfdsfsdf

edfsad

dsfsdfsdf

test

specific

var_miha

new_var_2

new_mih_var

mih_var

testheight

available

testulet

testvar

This is a plain text that will be inserted in an expandable heading for using this raw as an exampl

altscenario

This is a plain text that will be inserted in an expandable heading for using this raw as an example

scenario

exemplu

variabila

Archbee

text

refresh_token

YourBank

MyBank

variable_test_video

variable123

silviu

Bogdan_test

ferwhethgte

target1

google

support

product_name

productName1

companyLegalName

programName

customerName1

productName

Product_Name

Test

SEFAS

uptempo

customerName

testName

name1

customername

apilink1-getallmethod

variable_one

capitalize

company_name_adobe

jama_2

jama_1

domain

email

product

Glossary lets you define every tricky term, then gives them a sneak peek explanation on hover... Just like I'm doing with this text right here!