summaryrefslogtreecommitdiffstats
path: root/src/vagrant/kubeadm_istio
AgeCommit message (Collapse)AuthorFilesLines
2018-06-06fix istio deploy fialurewutianwei2-16/+5
Some files don't exist in istio 0.8.0 version. So it failed to deploy istio in CI. what this patch do: 1. using istio-demo.yml instead of istio.yml to deploy istio 2. define the ingress gateway when running bookinfo sample 3. rename ingress to ingressgateway Change-Id: I39ec39320d61e5af8282c6f50bad90240444bc79 Signed-off-by: wutianwei <wutianwei1@huawei.com>
2018-04-02fix deployment failureGuo Ruijing1-1/+1
Change-Id: I6145b406450b0846999223f1e4e6783eb06bb0a9 Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
2018-03-20Tiny fix for istio scenarioQiLiang3-3/+3
- disable user interactive when clean_bookinfo - run sleep before status check to save ci varify time Change-Id: I6072b85c3c941af30263101a3d4dca0537abf1fc Signed-off-by: QiLiang <liangqi1@huawei.com>
2018-03-08Basic setup for istio sidecar auto injectionQiLiang2-3/+41
To enable auto sidecar injection on specific namespace, you only need label the namespace with `istio-injection=enabled`, e.g.: kubectl label namespace default istio-injection=enabled For details please refer: https://istio.io/docs/setup/kubernetes/sidecar-injection.html#automatic-sidecar-injection Change-Id: I2059aa0be2ab3f4f942342850d286281c5f940d4 Signed-off-by: QiLiang <liangqi1@huawei.com>
2018-02-02Update istio installationQiLiang1-3/+15
Update istio installation, since upstream istio 0.5.0 is released. Fetch istio latest version from github.com instead of hard code it. Change-Id: If7aca736d631f74f9fdd6828a204895ec342b0ad Signed-off-by: QiLiang <liangqi1@huawei.com>
2018-01-21remove trailing spaceGuo Ruijing2-2/+2
Change-Id: I36903535289c51346deea49791fd4a0d6e223a18 Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
2018-01-19Add istio 0.4 installation on top of k8s 1.9Yapeng Wu8-0/+191
Based on k8s 1.9 (kubeadm_basic) installation, adding the istio 0.4 installation and simple validation. Change-Id: Iee2c71974fb2b33df0f9342e0bfd9e96e4dab8f5 Signed-off-by: Yapeng Wu <yapengwu@gmail.com>