Answer
This can simply be a resource-allocation issue at the VM level rather than a configuration mistake — restarting the VM that's hosting the stuck pods has resolved exactly this symptom, apparently because the expected resources weren't properly allocated to the node the first time around. Worth trying before digging further into ingress-specific configuration if the pods are stuck in PodInitializing with no informative error.