Trying to cover a scenario when user would only want to use Istio's ingress features by installing only relevant components. A guide is planned to be written.

Following is a summary of the issues encountered so far:

Citadel Always Included

When disabling all components but ingress, ingressgateway and pilot the following 4 pods are being installed:

NAME                                    READY     STATUS    RESTARTS   AGE
istio-citadel-64c9df88bc-wm5sw          1/1       Running   0          3m
istio-ingress-5d6896cdb5-l4nwf          1/1       Running   0          3m
istio-ingressgateway-7595bdb4bf-t8g55   1/1       Running   0          3m
istio-pilot-7ff65fbb95-d2wfg            2/2       Running   0          3m

istio-citadel is being installed because there is no toggle flag to disable its creation by helm.
PR #5675 is intended to allow this toggling.

Proxy Crash

Both ingress and ingressgateway fail to start with an error:

[2018-05-21 07:32:02.226][47][critical][main] external/envoy/source/server/server.cc:75] error initializing configuration '/etc/istio/proxy/envoy-rev0.json': malformed IP address: istio-statsd-prom-bridge

The reason is that the proxy is being provided with an arg --statsdUdpAddress=istio-statsd-prom-bridge:9125.
Removing this argument will keep proxy running.

Possible solutions:

• Modify proxy to avoid crash
• Update helm template to add the argument only if mixer is enabled. This is a little tricky because ingress chart can't access enabled flag of the mixer chart
• Ask the users to remove those args in the generated YAML

/cc @linsun @mandarjog @rshriram