bumpup istio & istio-provisoner addon 1.4.0 → 1.5.0

[govargo]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

This PR bump up istio & istio-operator addon's image v1.4.0 to v1.5.0

Which issue(s) this PR fixes:

Fixes #7118

Does this PR introduce a user-facing change?

Yes.
This image bumpup includes istio's bug fix & features.
https://github.com/istio/istio/releases/tag/1.5.0
https://istio.io/news/releases/1.5.x/announcing-1.5/

Before

$ minikube start --memory=8192mb --cpus=4
$ minikube addons enable istio-provisioner
$ minikube addons enable istio-provisioner

$ kubectl get pods -n istio-system -w
NAME                                      READY   STATUS             RESTARTS   AGE
istio-citadel-68bf6b66c-r7trn             1/1     Running            0          6m55s
istio-galley-6999d4d659-lzlj5             2/2     Running            0          6m55s
istio-ingressgateway-5fc59bb7fb-d878d     1/1     Running            0          6m53s
istio-pilot-578475b5bc-lxrtb              2/2     Running            0          6m53s
istio-policy-6df5d666d5-2vwf4             2/2     Running            5          6m54s
istio-sidecar-injector-6b4d8cdfb5-xk8dm   1/1     Running            0          6m53s
istio-telemetry-7487f698db-khrxh          1/2     Running            5          6m52s
prometheus-946f9f9d8-279pt                1/1     Running            0          6m56s

After

$ minikube start --memory=8192mb --cpus=4
$ minikube addons enable istio-provisioner
$ minikube addons enable istio-provisioner

$ kubectl get pods -n istio-system
NAME                                    READY   STATUS    RESTARTS   AGE
istio-ingressgateway-59d85f84c7-vq4rq   1/1     Running   0          3m40s
istiod-b8ffd7d4d-2j9ck                  1/1     Running   0          3m40s
prometheus-d78dbcffd-24j58              2/2     Running   0          3m42s

$ istioctl version
client version: 1.5.0
control plane version: 1.5.0
data plane version: 1.5.0 (2 proxies)

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

NONE

[k8s-ci-robot]

Hi @govargo. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: govargo
To complete the pull request process, please assign tstromberg
You can assign the PR to them by writing /assign @tstromberg in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[minikube-bot]

Can one of the admins verify this patch?

[govargo]

/assign @tstromberg