Define Custom Pod and Service Subnets

by default, the turbine platform installer uses 10 32 0 0/16 for podcidr and 10 96 0 0/16 for servicecidr if these are in use in your network and routable by the cluster nodes, the internal cluster ip ranges will need to be overridden however, the installer also includes logic to find an available subnet automatically anywhere in the 10 0 0 0/8 network as long as the excluded subnets appear in an ip route it should find one without conflicts to override the defaults, you can add servicecidr (under the kubernetes spec) and podcidr (under the flannel spec) to the installer override yaml patch file spec section for example apiversion cluster kurl sh/v1beta1 kind installer metadata name "patch" spec kubernetes servicecidr "\<your custom subnet>" flannel podcidr "\<your custom subnet>" alternatively, you can leave servicecidr blank, and set servicecidrrange to 16 or /16 then at install time, the installer will try to discover a /16 subnet to use, which does not overlap with any ip routes already present on the host if you provide an invalid cidr, you may run into issues with the installer hanging during the installation process see docid\ jhwb4tkprl ws43pk7g4w for instructions on how to specify the installer override file during the install and join node commands