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 configure ingress options enable ingress resource — enable this option if you have an existing ingress controller installed in your cluster that you want to use to expose turbine externally ingress resource annotations — enter the annotations to apply to the ingress resource see the documentation for your ingress controller for required annotations if your ingress controller requires a nodeport service, you must enable expose the swimlane web service externally ingress resource tls — enter the tls section for the ingress resource see your ingress controller’s documentation for 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 one per line, each starting with hostname example must be dns compliant up to 63 characters long only letters, numbers, and hyphens cannot start/end with a hyphen or contain consecutive hyphens if blank, all hostnames will match expose the swimlane web service externally — expose the swimlane web service as a nodeport from each node in the cluster swimlane web service port — enter the nodeport for the externally exposed swimlane web service if blank, a random port will be used set swimlane web service annotations — enter annotations for the swimlane web service upload a certificate for swimlane web backend — upload a certificate and key for the backend swimlane web service if none is uploaded, a self signed certificate will be used swimlane recommends configuring your ingress controller or load balancer with no request timeout, no idle timeout, and no request body size limit , so that these are limited only by swimlane web pods configure swimlane settings asp net hosting environment — development — sends stack traces to the browser for 500 errors production — does not send stack traces enable swimlane audit logging — logs raw api requests and responses into swimlane pods swimlane logging level — specify the logging level configure openssl settings decide whether to override the cipherstring and minprotocol values for outgoing secure connections 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 configure telemetry enable the opentelemetry collector — run an opentelemetry collector and connect it to an elastic apm service by providing the elastic apm url endpoint and secret token configure mongodb (external access) expose mongodb externally — expose each mongodb pod as a nodeport from each node in the cluster each will use a random port in your cluster's nodeport range configure certificates 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 configure turbine settings enable the turbine logger — log messages from all agents and reoutput them in a central location configure rabbitmq rabbitmq admin password — admin password for rabbitmq deployment rabbitmq turbine agent user password — password for the user remote agents use to connect rabbitmq erlang cookie — shared secret used for rabbitmq nodes to communicate configure rabbitmq storage rabbitmq volume size (gb) — persistent volume size in gb storageclass for rabbitmq data — storageclass to use for the rabbitmq persistent volume configure pod liveness probe choose whether to enable or disable liveness probes default api pods disabled, tasks pods enabled configure mongodb settings enter encryption keys and passwords for your swimlane database and mongodb you can skip this step if using an external mongodb cluster see deploy with an external mongodb cluster docid\ jjipz1a6vwbfcscofq rd do not change mongodb settings after installation doing so will break swimlane acceptable special characters !@#$%^& () =+/\[]| ;<,> ? configure mongodb storage mongodb volume size (gb) — persistent volume size in gb storageclass for mongodb data — storageclass to use for the mongodb persistent volume configure postgresql storage postgresql volume size (gb) — persistent volume size in gb storageclass for postgresql data — storageclass to use for the postgresql persistent volume configure ha environment 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 must be at least 3 and an odd number to ensure replica set failover works properly configure affinity settings use simple pod affinity — balance swimlane and mongodb pods across nodes if advanced affinity settings are required, disable simple affinity to reveal advanced options pod types without special requirements can be left blank see kubernetes affinity and anti affinity settings https //kubernetes io/docs/concepts/scheduling eviction/assign pod node/#affinity and anti affinity for valid 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 reassign pods to different nodes if your mongodb storageclass does not support pvcs across multiple nodes, changing these settings may cause deployment failures configure default tenant settings enter the default account id and default tenant id (optional) configure beta settings enter beta configuration settings and click save config preflight and deployment save the configuration to start preflight checks resolve any failed checks before proceeding once preflight checks pass, the turbine platform installer admin console opens