Configure the Turbine Platform for an Existing Cluster Install

when you need to access the turbine installer ui after the initial install you can proxy it again by running this command and accessing it in a chrome browser all configuration of the turbine installer and turbine platform must be done through the turbine installer 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 installer first, configure ingress options enable ingress resource enable this option if you have an existing ingress controller installed in your cluster that you want to utilize to expose turbine externally ingress resource annotations enter the annotations to apply to the ingress resource see the documentation for your ingress controller for the required annotations to work properly if your ingress controller requires a nodeport service then you must enabled the expose the swimlane web service externally option below ingress resource tls enter the tls section for the ingress resource see your ingress controller’s documentation for the required tls settings see the kubernetes documentation for valid ingress tls yaml https //kubernetes io/docs/concepts/services networking/ingress/#tls ingress resource hostnames enter the hostnames to match to this ingress resource enter one per line with each line starting with a dash and a space (e g " hostname example") you must use dns compliant records a dns record can be up to 63 characters long and can only contain letters, numbers, and hyphens the record cannot start or end with a hyphen, or have consecutive hyphens if left blank, it will match all hostnames expose the swimlane web service externally enable this option to expose the swimlane web service as a nodeport from each node in the cluster on the tcp port below you must configure your external layer 7 load balancer to forward to each node over the chosen port swimlane web service port enter the port to use for the externally exposed swimlane web service this port must be within your cluster's nodeport range if left blank, it will use a random port in your cluster's nodeport range set swimlane web service annotations enter the annotations to apply to the swimlane web service see the documentation for your ingress controller for the required annotations to work properly 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 swimlane recommends that you have your ingress controller or load balancer set to have no request timeout, no idle timeout, and no request body size limit so that these are limited only by the swimlane web pods 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 next, determine whether you want to enable opentelemetry collector and connect it to elastic apm enable the opentelemetry collector enable this option to run an opentelemetry collector and connect it to an elastic apm service by providing the elastic apm url endpoint and elastic apm secret token determine whether you want mongodb to be exposed for external access expose mongodb externally enable this option to expose each mongodb pod as a nodeport from each node in the cluster each one will use a random port in your cluster's nodeport range if you have third party certificates for api and tasks, click upload additional trusted certificates for api and tasks and then browse for and upload your certificates next, set the turbine settings enable the turbine logger enable this option to log messages coming from all agents and reoutput them in a central location next, define the rabbitmq settings rabbitmq admin password the admin password for the rabbitmq deployment rabbitmq turbine agent user password the password for the user that remote agents will use when connecting to this deployment rabbitmq erlang cookie the shared secret used for the rabbitmq deployment nodes to communicate to one another next, define the rabbitmq volume size and storageclass rabbitmq volume size (gb) the size in gb for the rabbitmq persistent volume storageclass for rabbitmq data the storageclass to use for the rabbitmq persistent volume 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 is disabled and for tasks pods is enabled on initial mongodb settings, enter the appropriate encryption keys and passwords for your swimlane database and mongodb you can skip steps 7 and 8 if you are using an external mongodb cluster for more information, see deploy with an external mongodb cluster docid\ jjipz1a6vwbfcscofq rd 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 !@#$%^& () =+/\[]| ;<,> ?` next, set the mongodb volume size and storageclass mongodb volume size (gb) the size in gb for the mongodb persistent volume storageclass for mongodb data the storageclass to use for the mongodb persistent volume next, set the postgresql volume size and storageclass postgresql volume size (gb) the size in gb for the postgresql persistent volume storageclass for postgresql data the storageclass to use for the postgresql persistent volume ss next, set the ha environment settings for this cluster enable this to set the number of pods of each type to run these settings should only be enabled if your cluster has 3 or more nodes if you are installing on a single node deployment this option should not be enabled the number of mongodb replicas value must be at least 3 and be an odd number to ensure the replica set primary failover can happen properly when needed next, set the affinity settings use simple pod affinity use simplified affinity options to decide how to balance the swimlane and mongodb pods across your cluster nodes if you need to set more advanced affinity settings then disable the use simple pod affinity option to show the advanced settings fields pod types that don't require special settings can be left blank see the kubernetes affinity and anti affinity settings topic documentation for valid affinity yaml swimlane recommends that you have the swimlane pods prefer to be scheduled on separate cluster nodes but able to run multiple pods of each type on the same cluster node if the affinity rule cannot be satisfied swimlane also recommends that you have the mongodb and rabbitmq pods require to be scheduled on separate cluster nodes running multiple mongodb pods on the same cluster node may cause resource conflicts changing affinity settings can change the nodes that pods are running on if the storageclass chosen for the mongodb pods does not support pvcs being accessed by multiple cluster nodes then changing the mongodb affinity settings may result in the config change failing to deploy next, from the default tenant settings , enter the default account id and default tenant id 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