Sync metadata folder from master to v1-branch

[zhenghuiwang]

This PR fixes the issue of v1-branch that metadata-db deployments can't be connected from other pods.

The cause is that v1-branch misses some istio-sidecar annotations. This PR adds them back to v1-branch.

[kubeflow-bot]

This change is 

[richardsliu]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: richardsliu

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:

• metadata/OWNERS [richardsliu]

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

[zhenghuiwang]

/test kubeflow-manifests-presubmit

[zhenghuiwang]

/retest

[k8s-ci-robot]

@zhenghuiwang: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
kubeflow-manifests-presubmit	bfc7216	link	/test kubeflow-manifests-presubmit

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[zhenghuiwang]

@kunmingg the above tests for manifest v1.0-branch are broken due to KFAM. Do you know what changes from master need to be cherry picked?

/cc @kunmingg

[jlewi]

/hold

[jlewi]

See: kubeflow/kfctl#296

I'm not sure this is the correct way to fix the issue. Per kubeflow/kfctl#296 the problem right now is that newer versions of kfctl are not backwards compatible with existing 1.0 configs because they turn on istio side car injection.

This change would be a forward fix that requires people to use newer versions of manifests with the newer versions of kfctl.

I think the ideal fix would be to figure out how to make kfctl backwards compatible; i.e. not turn on istio side car injection in the kubeflow namespace for 1.0 manifests.