--- title: Automate an Online Embedded Installation slug: install-10x/automate-an-online-embedded-installation docTags: createdAt: 2025-07-16T13:29:40.583Z --- This topic provides automation steps for setting up an online, single-node Swimlane installation on embedded clusters. ## Installation Preparation and Customization Before you begin, review the [System Requirements for an Embedded Cluster Install](docId\:LD6YzgAX-gPbBdT2c1h3S) 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 [Overriding Installer Settings](docId\:X7jKIJjG4IP6y3FqQqxyI) for more options. ### Installer Patch File Example Here is an example installer patch file: :::BlockQuote apiVersion: "cluster.kurl.sh/v1beta1" kind: "Installer" metadata: name: "patch" spec: kubernetes: HACluster: true loadBalancerAddress: "\:6443" firewalldConfig: disableFirewalld: true selinuxConfig: disableSelinux: true ::: You also need the following files: - Swimlane Platform Installer license file (ends with `.yaml`) - Swimlane license file (ends with `.lic`) ## Embedded Cluster Installation 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=.yaml` ## Swimlane Installation and Deployment After the embedded Kubernetes cluster has been installed, install Swimlane with the following command: :::BlockQuote kubectl kots install swimlane-platform \\ \--namespace default \\ \--shared-password \ \\ \--license-file \.yaml \\ \--port-forward=false \\ \--config-values \.yaml ::: ### Creating an SPI Config File The `.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 ` This command downloads a copy of the entire SPI deployment specifications to a local folder named `swimlane-platform`. The config file is located at `./swimlane-platform/upstream/userdata/config.yaml` in the downloaded folder. To create the file manually, review the configurable options available in the [Embedded Cluster SPI](docId\:uaYKeaEqkgLr5TPEzNLxQ). Here is a basic version of the config file that you can use for an initial single-node configuration: :::BlockQuote apiVersion: kots.io/v1beta1 kind: ConfigValues metadata: creationTimestamp: null name: swimlane spec: values: is\_ha: value: "0" mongo\_admin\_user\_password: value: \ mongo\_admin\_user\_password\_confirm: value: \ mongo\_swimlane\_user\_password: value: \ mongo\_swimlane\_user\_password\_confirm: value: \ swimlane\_database\_encrypt\_key: value: \ swimlane\_database\_encrypt\_key\_confirm: value: \ swimlane\_enable\_ingress: value: "1" swimlane\_hostname: value: \ ::: ## Swimlane Initial Login 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: :::BlockQuote kubectl wait -l statefulset.kubernetes.io/pod-name=swimlane-sw-mongo-0 --for=condition=ready pod --namespace \ --timeout=240s export SW\_API=$(kubectl get po -n \ --no-headers -o custom-columns="\:metadata.name" | grep -i api)   kubectl wait --for=condition=ready pod $SW\_API -n \ --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:///api/settings/license/upload -H 'Content-Type: multipart/form-data' -F file=@.lic` Then, to create the initial administrative user, insert the returned JSON into the following curl command: :::BlockQuote curl -kLv -X POST https\://\/api/settings/install \\ \--header "Content-Type: application/json" \\ -d '\{"mailSettings":\{}, "password":"\","confirmPassword":"\", "databaseEncryptionKey":"", "swimlaneUrl":"https\://\", "license" :\, "adminUserName":"\", "adminEmail":"\"}' :::