Configure the Turbine Platform for an Embedded Cluster Install

when you need to access the tpi ui after the initial install you can access it by access port 8800 over https on any node ip (e g https // 8800) all configuration of the turbine platform installer and turbine platform must be done through the tpi admin console config page editing or manipulating the underlying kubernetes resources is not supported and will not be permanent since they are managed and controlled by the turbine platform installer on swimlane settings, you'll begin setting up your configuration for turbine review and set the following fields as necessary expose the swimlane web service externally? enable this option when using a layer 7 load balancer the swimlane web service will be directly exposed from each node in the cluster on tcp port 4443 enable the ingress controller enable this option when using a layer 4 load balancer or for single node lab/test environments the included ingress controller will be used for routing web requests to swimlane on tcp port 443 swimlane hostname the dns record pointing to the turbine platform installer and turbine platform load balancer mandatory upload a certificate for swimlane web? enable this option to upload a certificate and key to be used for the included ingress controller if no certificate is uploaded a self signed one will be generated and used the certificate must be ascii encoded x 509 format the private key cannot be password protected upload a certificate for swimlane web backend? enable this option to upload a certificate and key to be used by the backend swimlane web service if no certificate is uploaded a self signed one will be used on swimlane settings, you'll begin setting up your configuration for turbine review and set the following fields as necessary next, set the swimlane settings asp net hosting environment set this option to development to have stack traces sent to the browser for 500 errors set this option to production to not send them enable swimlane audit logging enable this option to log raw swimlane api requests and responses into swimlane pods swimlane logging level set this option to specify the logging level for swimlane pods next, determine whether to override the openssl settings for cipherstring and minprotocol for outgoing secure connections that originate from api and tasks pods since outgoing secure connections include requests to the swimlane api service, there are limitations to what can be set for these values in order to not break your deployment of swimlane minprotocol should not be set to anything higher than tlsv1 2, and cipherstring can be set to the highest security level like high\@seclevel=5 or default\@seclevel=5 the turbine settings field allows you to increase or decrease the size of the git repository, with a default size of 100 mb next, choose whether to enable or disable a pod liveness probe for the api and tasks pods the default liveness probe setting for api pods and tasks pods is enabled on initial mongodb settings, enter the mongo encryption keys and administrative passwords for mongodb you can skip this step if you are using an external mongodb cluster for more information, see deploy with an external mongodb cluster docid 4z bhymwnvyvrloycg0kj do not change the mongodb settings after installation doing so will break your deployment of swimlane here are the acceptable special characters to use in keys and passwords !@#$%^& () =+/\[]| ;<,> ?` passwords are mandatory turbine cloud settings configuration \ the turbine cloud settings section is used to configure the api connection between the swimlane platform and turbine cloud this configuration ensures secure and authorized access to the cloud environment for more information, contact swimlane support next, if you have 3 or more nodes in your cluster, click ha environment and set the number of pods for each type the number of mongodb replicas must be at least 3 and an odd number once you have multiple mongodb replicas, you cannot go down to one enter values for all the fields shown in the following video to ensure proper configuration if you have an ha cluster, confirm the recommended default settings for swimlane web/api/tasks/reports and turbine api/engine/agent/webhookagent/websocket relay antiaffinity (soft) and mongodb and rabbitmq pod antiaffinity (hard) then, click save config the mongodb pod antiaffinity settings should not be changed after installation doing so could break your deployment of turbine next, from the default tenant settings , enter the default account id and default tenant id (not mandatory) next, enter the beta configuration settings and click save config when you save the configuration, preflight checks for your installation begin once the preflight checks process, the turbine platform installer admin console opens for version 24 3 x of the turbine platform, if you encounter any issues with swimlane tenant pods related to the database during a new installation, redeploy the application no action is required if you are upgrading once the status of your application says ready , you have a successful installation of turbine turbine 23 2 1 comes out of the box with a privileged default user swimlane system this account uses a default, well known password it is critical that you reset this password immediately after successful deployment after logging into the ui, reset the “swimlane system” user password with a unique, complex password when this password is changed, it may result in the swimlane system user account getting locked the account can be unlocked by the superadmin account used to reset the password