Answer
The installer's autodetection of inactive components depends on solutionset.yaml being present and correctly located relative to ifscloud-values.yaml, and on the delivery being run from the proper ifsroot folder structure — if the delivery zip (as produced by BuildPlace) still has an extra wrapper folder around its contents that wasn't removed before extraction, or the files aren't in the expected relative locations, the installer won't correctly detect which components are inactive and will deploy pods for all of them regardless. Fixing the folder structure so autodetection works correctly is the supported path; scaling replicas to 0 manually works as a stopgap but has to be redone on every delivery until the underlying structure issue is fixed.