Overriding Installer Settings

\<cases for overriding>\<location?> certain turbine platform installer settings can be overridden at install time to ensure proper installation and cluster operation creating the override patch file create the base patch file named override yaml with the following contents apiversion cluster kurl sh/v1beta1 kind installer metadata name "" spec adding override options to the patch file installer settings overrides are then added under the spec section of the override yaml patch file see the topics below for more information about how to override available settings define high availability and load balancer settings docid\ zybcvghymedi3szkotwaf define custom pod and service subnets docid\ qunhxryi23les7qgzoyp1 define proxy settings docid 4rkkazfikddzy yoveyby install with firewalld enabled docid\ rbej8z n wummis3 hgs8 install with selinux enabled docid\ vvnjeoejt5yfv5q3wcsgh using the override patch file the patch file then needs to be specified as an argument to all install, upgrade, and node join commands to ensure the overrides are obeyed installer spec file=\<path to installer override yaml> install command example with the override patch file specified curl ssl https //kurl sh/turbine stable multitenant | sudo bash s ha installer spec file=installer override yaml> join node command example with the override patch file specified curl ssl https //kurl sh/turbine/join sh | sudo bash s \ kubernetes master address=ip\ port \ kubeadm token=token \ kubeadm token ca hash=sha256\ hash \ docker registry ip=ip \ kubernetes version=ip \ cert key=key \ control plane \ installer spec file=\<path to installer override yaml>