On AWS how can I use internal itsio-ingress rather than internet-facing?

[manojlds]

Setup kubeflow based on - https://raw.githubusercontent.com/kubeflow/manifests/v1.2-branch/kfdef/kfctl_aws.v1.2.0.yaml

The Istio ingress is public facing, doesn't have dns, acm cert etc. I see that there is a secure overlay but with my minimal understanding of Kustomize, not sure how to use this version or do proper patching.

Trying to do something like this in the config file:

  - kustomizeConfig:
      repoRef:
        name: manifests
        path: aws/istio-ingress/overlays/secure
    name: istio-ingress

Gives the following error on kfctl apply:

kfctl exited with error: failed to apply:  (kubeflow.error): Code 500 with message: kfApp Apply failed for kustomize:  (kubeflow.error): Code 500 with message: error evaluating kustomization manifest for istio-ingress: accumulating resources: recursed accumulation of path '../../.cache/manifests/manifests-1.2.0/aws/istio-ingress/overlays/secure': merging from generator &{0xc003846000 0xc001333d80 { } {map[] map[] true} {{ istio-ingress-config merge {[] [] [params.env] }}}}: id resid.ResId{Gvk:gvk.Gvk{Group:"", Version:"v1", Kind:"ConfigMap"}, Name:"istio-ingress-config", Namespace:""} does not exist; cannot merge or replace

Any suggestions on this issue, or how to achieve some customization on the istio-ingress would be helpful.

On a related note, is there a way to quickly apply only the istio changes rather than doing kfctl apply and let it go through the entire manifests?

[manojlds]

This issue was useful and I was able to get things sorted - #1549
Closing this.