Two examples for disabling istio injection in kubeflow namespace

[Bobgy]

Which issue is resolved by this Pull Request:
Example of #700
Part of kubeflow/pipelines#1223
Unblocks kubeflow/kfctl#131

Description of your changes:
Add istio disable injection annotations for two deployments.

Checklist:

• Unit tests have been rebuilt:
  1. cd manifests/tests
  2. make generate-changed-only
  3. make test

---

This change is 

[Bobgy]

/cc @jlewi

[Bobgy]

One problem I realized though, is that, pods generated by all the services also need such annotations. It is not an easy task to adjust every service to let them work in Kubeflow.

I'd still prefer changing cluster default to not inject pods with sidecars.

[jlewi]

One problem I realized though, is that, pods generated by all the services also need such annotations. It is not an easy task to adjust every service to let them work in Kubeflow.

What's the difficulty?

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jlewi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jlewi]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Bobgy]

@jlewi Not exactly difficult, but it's a lot of work to make sure each operator spawn pod (like argo) has an annotation to disable sidecar injection. You should have more context on this. If there isn't many, it's fine.