Installing IFS Cloud as a remote/on-prem deployment with separate Ubuntu (Kubernetes) and Windows (Management Server) hosts — running the installer's main.ps1 script fails with a Kubernetes-cluster-unreachable error if ManagementServerIP is left blank in the config, and fails with kubectl unable to connect to the server if the Windows Server IP is filled in instead.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

This points to the kubeconfig file for the Kubernetes cluster not having been correctly retrieved and placed on the Windows Management Server before running main.ps1 — the installer's PowerShell script and kubectl both need a valid kubeconfig pointing at the actual Kubernetes cluster on the Linux host to reach it, and without that step done correctly first, filling in either the blank or the Windows Server IP in the config just produces a different flavor of the same underlying connectivity failure. Revisit the server-preparation documentation step specifically covering how to fetch the kubeconfig file from the Kubernetes cluster on the middle-tier server and copy it to the Windows Management Server before re-running the installer.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions