During a 23R1 remote/clustered installation, several ifs-ingress-related pods (linkerd components, the nginx ingress controller and default backend) never come up, with no errors logged anywhere in the install logs or the ingress install log specifically.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Two configuration mismatches are worth checking carefully in main_config.json: the Dns value needs to contain only actual DNS server addresses (not a stray public resolver address mixed in incorrectly), and the HelmVersion value needs to match exactly what's specified in main_config.json.template — a HelmVersion that's drifted out of sync between your config and the template has caused exactly this kind of silent ingress-pod-never-starts failure with no explicit error surfaced anywhere in the logs.

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