Create a new cluster for chatbot based on the GCP blueprint.

[jlewi]

• We want to create a webhook to respond to Dialogflow. To do that we need be able to modify the ISTIO ingress policy in order to apply different JWT validation for requests routed through IAP vs calls from DialogFlow.

• I initially tried that using ISTIO 1.1 and ran into problems. On ISTIO 1.4 it seemed to work.

• So this PR defines a new cluster based on the Kubeflow GCP blueprint so using ASM which has ISTIO 1.4. It is also using ACM to manage the deployment.

• Related to #142

[kubeflow-bot]

This change is 

[jlewi]

@hamelsmu mind taking a quick look at this?

[k8s-ci-robot]

The following users are mentioned in OWNERS file(s) but are not members of the kubeflow org.

Once all users have been added as members of the org, you can trigger verification by writing /verify-owners in a comment.

• lluunn
  • kubeflow_clusters/code-intelligence/upstream/manifests/OWNERS
  • kubeflow_clusters/code-intelligence/upstream/manifests/istio-1-3-1/OWNERS
  • kubeflow_clusters/code-intelligence/upstream/manifests/istio/OWNERS
  • kubeflow_clusters/code-intelligence/upstream/manifests/jupyter/OWNERS
  • kubeflow_clusters/code-intelligence/upstream/manifests/kfdef/OWNERS
• mameshin
  • kubeflow_clusters/code-intelligence/upstream/manifests/aws/OWNERS

[hamelsmu]

/lgtm /approve

This PR changes an epic number of files

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hamelsmu

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](https://github.com/kubeflow/code-intelligence/blob/master/OWNERS)~~ [hamelsmu] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment