text:
Error from server (InternalError): error when creating "samples/bookinfo/networking/bookinfo-gateway.yaml": Internal error occurred: failed calling admission webhook "pilot.validation.istio.io": Post https://istio-galley.istio-system.svc:443/admitpilot?timeout=30s: dial tcp 10.254.176.80:443: connect: connection timed out

Describe the bug
{{ Succinctly describe the bug }}
Expected behavior
{{ What did you expect to happen? }}
Steps to reproduce the bug
{{ Minimal steps to reproduce the behavior }}
Version
{{ What version of Istio and Kubernetes are you using? Use istioctl version and kubectl version }}
Installation
{{ Please describe how Istio was installed }}
Environment
{{ Which environment, cloud vendor, OS, etc are you using? }}
Cluster state
{{ If you're running on Kubernetes, consider following the
instructions
to generate "istio-dump.tar.gz", then attach it here by dragging and dropping
the file onto this issue. }}

@Linuxbody Can you check your  galley service by
kubectl get svc -n istio-system

kubectl get svc,endpoints -n istio-system|grep ga
service/istio-egressgateway      NodePort    10.254.158.174           80:31435/TCP,443:32910/TCP                                                                                3d
service/istio-galley             ClusterIP   10.254.129.150           443/TCP,9093/TCP                                                                                3d
service/istio-ingressgateway     NodePort    10.254.226.196           80:31380/TCP,443:31390/TCP,31400:31400/TCP,15011:43906/TCP,8060:32826/TCP,853:37592/TCP,15030:40785/TCP,15031:44695/TCP   3d
endpoints/istio-egressgateway      192.168.169.168:80,192.168.169.168:443                                        3d
endpoints/istio-galley             192.168.169.167:9093,192.168.169.167:443                                      3d
endpoints/istio-ingressgateway     192.168.169.148:80,192.168.169.148:15030,192.168.169.148:15011 + 5 more...    3d

Check if your galley service accessible?

@hzxuzhonghu
logs:
kubectl -n istio-system logs -f istio-galley-58f566cb66-556db
warn    istio-galley validatingwebhookconfiguration update deferred: istio-system/istio-galley endpoint not ready: no subsets
2018-11-20T14:06:20.187377Z     warn    istio-galley validatingwebhookconfiguration update deferred: istio-system/istio-galley endpoint not ready: no subsets
2018-11-20T14:06:25.184009Z     warn    istio-galley validatingwebhookconfiguration update deferred: istio-system/istio-galley endpoint not ready: no subsets

[root@k8s-master1 istio-1.0.3]# kubectl -n istio-system get po,svc
NAME                                         READY     STATUS      RESTARTS   AGE
pod/grafana-59b787b9b-55rk9                  1/1       Running     0          8m
pod/istio-citadel-78df8c67d9-qkj94           1/1       Running     0          8m
pod/istio-cleanup-secrets-bg477              0/1       Completed   0          8m
pod/istio-egressgateway-6b96cd7f5-pkd7f      1/1       Running     0          8m
pod/istio-galley-58f566cb66-556db            1/1       Running     0          8m
pod/istio-grafana-post-install-7tcgg         0/1       Completed   0          8m
pod/istio-ingressgateway-6cbbf596f6-zfdcj    1/1       Running     0          8m
pod/istio-pilot-76474d9d49-tm4vq             2/2       Running     0          8m
pod/istio-policy-6b99d88bc5-fmfg5            2/2       Running     0          8m
pod/istio-security-post-install-64f9h        0/1       Completed   0          8m
pod/istio-sidecar-injector-b88dfb954-whlq4   1/1       Running     0          8m
pod/istio-telemetry-675cb4cb9d-8xmb6         2/2       Running     0          8m
pod/istio-tracing-7596597bd7-pcsqr           1/1       Running     0          8m
pod/prometheus-76db5fddd5-7x72x              1/1       Running     0          8m
pod/servicegraph-fc55fc579-vcd47             1/1       Running     0          8m
NAME                             TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)                                                                                AGE
service/grafana                  ClusterIP      10.254.28.187            3000/TCP                                                                                8m
service/istio-citadel            ClusterIP      10.254.46.17             8060/TCP,9093/TCP                                                                                8m
service/istio-egressgateway      ClusterIP      10.254.18.155            80/TCP,443/TCP                                                                                8m
service/istio-galley             ClusterIP      10.254.173.220           443/TCP,9093/TCP                                                                                8m
service/istio-ingressgateway     LoadBalancer   10.254.47.132         80:31380/TCP,443:31390/TCP,31400:31400/TCP,15011:34019/TCP,8060:40045/TCP,853:34557/TCP,15030:30001/TCP,15031:38852/TCP   8m
service/istio-pilot              ClusterIP      10.254.9.95              15010/TCP,15011/TCP,8080/TCP,9093/TCP                                                                                8m
service/istio-policy             ClusterIP      10.254.140.193           9091/TCP,15004/TCP,9093/TCP                                                                                8m
service/istio-sidecar-injector   ClusterIP      10.254.212.72            443/TCP                                                                                8m
service/istio-telemetry          ClusterIP      10.254.203.18            9091/TCP,15004/TCP,9093/TCP,42422/TCP                                                                                8m
service/jaeger-agent             ClusterIP      None                     5775/UDP,6831/UDP,6832/UDP                                                                                8m
service/jaeger-collector         ClusterIP      10.254.74.131            14267/TCP,14268/TCP                                                                                8m
service/jaeger-query             ClusterIP      10.254.177.16            16686/TCP                                                                                8m
service/prometheus               ClusterIP      10.254.1.58              9090/TCP                                                                                8m
service/servicegraph             ClusterIP      10.254.152.121           8088/TCP                                                                                8m
service/tracing                  ClusterIP      10.254.211.213           80/TCP                                                                                8m
service/zipkin                   ClusterIP      10.254.35.254            9411/TCP                                                                                8m[root@k8s-master1 istio-1.0.3]# kubectl -n istio-system get po,svc
NAME                                         READY     STATUS      RESTARTS   AGE
pod/grafana-59b787b9b-55rk9                  1/1       Running     0          8m
pod/istio-citadel-78df8c67d9-qkj94           1/1       Running     0          8m
pod/istio-cleanup-secrets-bg477              0/1       Completed   0          8m
pod/istio-egressgateway-6b96cd7f5-pkd7f      1/1       Running     0          8m
pod/istio-galley-58f566cb66-556db            1/1       Running     0          8m
pod/istio-grafana-post-install-7tcgg         0/1       Completed   0          8m
pod/istio-ingressgateway-6cbbf596f6-zfdcj    1/1       Running     0          8m
pod/istio-pilot-76474d9d49-tm4vq             2/2       Running     0          8m
pod/istio-policy-6b99d88bc5-fmfg5            2/2       Running     0          8m
pod/istio-security-post-install-64f9h        0/1       Completed   0          8m
pod/istio-sidecar-injector-b88dfb954-whlq4   1/1       Running     0          8m
pod/istio-telemetry-675cb4cb9d-8xmb6         2/2       Running     0          8m
pod/istio-tracing-7596597bd7-pcsqr           1/1       Running     0          8m
pod/prometheus-76db5fddd5-7x72x              1/1       Running     0          8m
pod/servicegraph-fc55fc579-vcd47             1/1       Running     0          8m
NAME                             TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)                                                                                AGE
service/grafana                  ClusterIP      10.254.28.187            3000/TCP                                                                                8m
service/istio-citadel            ClusterIP      10.254.46.17             8060/TCP,9093/TCP                                                                                8m
service/istio-egressgateway      ClusterIP      10.254.18.155            80/TCP,443/TCP                                                                                8m
service/istio-galley             ClusterIP      10.254.173.220           443/TCP,9093/TCP                                                                                8m
service/istio-ingressgateway     LoadBalancer   10.254.47.132         80:31380/TCP,443:31390/TCP,31400:31400/TCP,15011:34019/TCP,8060:40045/TCP,853:34557/TCP,15030:30001/TCP,15031:38852/TCP   8m
service/istio-pilot              ClusterIP      10.254.9.95              15010/TCP,15011/TCP,8080/TCP,9093/TCP                                                                                8m
service/istio-policy             ClusterIP      10.254.140.193           9091/TCP,15004/TCP,9093/TCP                                                                                8m
service/istio-sidecar-injector   ClusterIP      10.254.212.72            443/TCP                                                                                8m
service/istio-telemetry          ClusterIP      10.254.203.18            9091/TCP,15004/TCP,9093/TCP,42422/TCP                                                                                8m
service/jaeger-agent             ClusterIP      None                     5775/UDP,6831/UDP,6832/UDP                                                                                8m
service/jaeger-collector         ClusterIP      10.254.74.131            14267/TCP,14268/TCP                                                                                8m
service/jaeger-query             ClusterIP      10.254.177.16            16686/TCP                                                                                8m
service/prometheus               ClusterIP      10.254.1.58              9090/TCP                                                                                8m
service/servicegraph             ClusterIP      10.254.152.121           8088/TCP                                                                                8m
service/tracing                  ClusterIP      10.254.211.213           80/TCP                                                                                8m
service/zipkin                   ClusterIP      10.254.35.254            9411/TCP                                                                                8m

Could you try deleting the istio-galley validatingwebhookconfiguration and seeing what happens? Galley doesn't create the configuration until the endpoint is ready.
That said, even if a previous configuration was leftover, the logs below show that despite the endpoint being ready (via kubectl get), the logs showing the endpoint is not ready. I'm not sure what to make of that.

2018-11-20T14:06:25.184009Z warn istio-galley validatingwebhookconfiguration update deferred: istio-system/istio-galley endpoint not ready: no subsets

kubectl get svc,endpoints -n istio-system|grep galley
endpoints/istio-galley 192.168.169.167:9093,192.168.169.167:443 3d

What k8s provider / distribution are you using?

2018-11-20T14:06:20.187377Z warn istio-galley validatingwebhookconfiguration update deferred: istio-system/istio-galley endpoint not ready: no subsets

This is the cause.

https://github.com/istio/istio/issues/9998#issuecomment-440146973 shows a istio-galley endpoint with address 192.168.169.167:443. It's not clear if that was was captured at roughly the same time or not as the logs, or if there is a transient endpoint readiness issue.

Notice that, weird

Check this:
kubectl get ep -n istio-system istio-galley -oyaml

[root@k8s-master1 ~]# kubectl get ep -n istio-system istio-galley -oyaml
apiVersion: v1
kind: Endpoints
metadata:
creationTimestamp: 2018-11-20T14:05:56Z
labels:
istio: galley
name: istio-galley
namespace: istio-system
resourceVersion: "1804656"
selfLink: /api/v1/namespaces/istio-system/endpoints/istio-galley
uid: 664f02a7-eccd-11e8-8c32-000c29f04163
subsets:

addresses:

ip: 192.168.36.95
nodeName: k8s-node1
targetRef:
kind: Pod
name: istio-galley-58f566cb66-556db
namespace: istio-system
resourceVersion: "1706974"
uid: 66642f61-eccd-11e8-8c32-000c29f04163
ports:
name: http-monitoring
port: 9093
protocol: TCP
name: https-validation
port: 443
protocol: TCP

＃9998（注释）显示了一个地址为192.168.169.167:443的istio-galley端点。目前尚不清楚是否与日志大致同时捕获，或者是否存在暂时的端点准备问题。
@ayj
Self-built kubernetes, version 1.11.3 ;
After removing istio-galley, the same error

[root@k8s-master1 ~]# kubectl -n istio-system delete pod istio-galley-58f566cb66-556db
pod "istio-galley-58f566cb66-556db" deleted
[root@k8s-master1 ~]# kubectl -n istio-system get pod
NAME                                     READY     STATUS      RESTARTS   AGE
grafana-59b787b9b-55rk9                  1/1       Running     0          18h
istio-citadel-78df8c67d9-qkj94           1/1       Running     0          18h
istio-cleanup-secrets-bg477              0/1       Completed   0          18h
istio-egressgateway-6b96cd7f5-pkd7f      1/1       Running     0          18h
istio-galley-58f566cb66-2kt8r            1/1       Running     0          8s
istio-grafana-post-install-7tcgg         0/1       Completed   0          18h
istio-ingressgateway-6cbbf596f6-zfdcj    1/1       Running     0          18h
istio-pilot-76474d9d49-tm4vq             2/2       Running     0          18h
istio-policy-6b99d88bc5-fmfg5            2/2       Running     0          18h
istio-security-post-install-64f9h        0/1       Completed   0          18h
istio-sidecar-injector-b88dfb954-whlq4   1/1       Running     0          18h
istio-telemetry-675cb4cb9d-8xmb6         2/2       Running     0          18h
istio-tracing-7596597bd7-pcsqr           1/1       Running     0          18h
prometheus-76db5fddd5-7x72x              1/1       Running     0          18h
servicegraph-fc55fc579-vcd47             1/1       Running     0          18h
[root@k8s-master1 ~]# kubectl -n istio-system logs -f istio-galley-58f566cb66-2kt8r
2018-11-21T08:14:16.931343Z     info    server-side configuration validation enabled
2018-11-21T08:14:21.933690Z     info    istio-galley validatingwebhookconfiguration (re)loaded:
apiVersion: admissionregistration.k8s.io/v1beta1
kind: ValidatingWebhookConfiguration
metadata:
creationTimestamp: null
labels:
app: istio-galley
chart: galley-1.0.3
heritage: Tiller
release: istio
name: istio-galley
namespace: istio-system
ownerReferences:

apiVersion: extensions/v1beta1
blockOwnerDeletion: true
controller: true
kind: Deployment
name: istio-galley
uid: 66a930d8-eccd-11e8-869d-000c2967d19f
webhooks:
clientConfig:
caBundle: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUM1akNDQWM2Z0F3SUJBZ0lSQUxXRHZodjZLeWd6V25QcTVZVCtibnd3RFFZSktvWklodmNOQVFFTEJRQXcKSERFYU1CZ0dBMVVFQ2hNUmF6aHpMbU5zZFhOMFpYSXViRzlqWVd3d0hoY05NVGd4TVRJd01UUXdOakF6V2hjTgpNVGt4TVRJd01UUXdOakF6V2pBY01Sb3dHQVlEVlFRS0V4RnJPSE11WTJ4MWMzUmxjaTVzYjJOaGJEQ0NBU0l3CkRRWUpLb1pJaHZjTkFRRUJCUUFEZ2dFUEFEQ0NBUW9DZ2dFQkFMd05HZGRHM3psTWJ3NlNkQUVXOUw5VnlxUU0KbVBjZUVVK2FZL3lZS3ZnVnFVMGVHaWl2bkIzb05tbFpUUDRhZU1mOTdCWjUwRTFIeWxTeE82L21rY2YycWVvcwp0b0d6TkV3VktoTC9oY3JXV2d1L0cwNWg5SCtTSlJQcThIRVNKNTV4K0NvSXBoNzlKZm12NVoyTE1Zc0ZSaC95CkNaZVNOREx6N2E1K0lud2Z4VEVoRjllWUIwdVVpWjlrRmZXUUt6dW50d2NUN1g0OWxYUng3eTQ3ZzBkQ0FtdlgKYXNqUDl1bkpSLzFVVDArRWkwQmtPWFM0NUg1NXl6NkpiZUZva2ViVEljdTd6Zk1yL3NtaXhjenNlMXFsSDQwSwpYYjcyTUhuRnlCcmpNK2VyckduMWVxY3ZzS2FsUDQzQnozN3c3R014bExha0ZXdU1IV2JSRVNQSXVNTUNBd0VBCkFhTWpNQ0V3RGdZRFZSMFBBUUgvQkFRREFnSUVNQThHQTFVZEV3RUIvd1FGTUFNQkFmOHdEUVlKS29aSWh2Y04KQVFFTEJRQURnZ0VCQUhlV3pWUmJYZ1owTVdleG5GQ2tZRjREY0RuOWlFck5kWDNEZXlwR1BYLy9JcG1VaXhIVgp4K0tpN2plbjAydUR2VzAwS05PcE1Wdk5FRjBNMkdrbElCRUI1RHFuYkc2MktoUng1NXdtREd4TVVyM3ZsaDVxCjJpUnBIYmltSFlEZlhaQ1ptNXNmVGJBMFNZazdVeS9HRDVEVFdGaDZlZTVZNDFYVG1IS2k1TFVEMW1COFVmaVgKWHBDT01MNWpibm1hZ08yTXdDcGlCN29CQy9yOEVNY3BqUHJjNnU1WWVhTWFiU1JrREhNZ25IUldwNzFLdDdWMApwM1VhS0NjYzFtekROTkpRWmpQTW1VZk1nQWgvcHJMRzlBdG5KbzBiQnZSK1F3TnViZDdldU92b2x6NytRanNjCk43YWYzS2p2clM2V1YwUkFvZGJvcnd2Si9rbDlPcnJYdlBJPQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg==
service:
name: istio-galley
namespace: istio-system
path: /admitpilot
failurePolicy: Fail
name: pilot.validation.istio.io
namespaceSelector: {}
rules:

apiGroups:

config.istio.io
apiVersions:
v1alpha2
operations:
CREATE
UPDATE
resources:
httpapispecs
httpapispecbindings
quotaspecs
quotaspecbindings

apiGroups:

rbac.istio.io
apiVersions:
'*'
operations:
CREATE
UPDATE
resources:
'*'

apiGroups:

authentication.istio.io
apiVersions:
'*'
operations:
CREATE
UPDATE
resources:
'*'

apiGroups:

networking.istio.io
apiVersions:
'*'
operations:
CREATE
UPDATE
resources:
destinationrules
envoyfilters
gateways
serviceentries
virtualservices

clientConfig:
caBundle: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUM1akNDQWM2Z0F3SUJBZ0lSQUxXRHZodjZLeWd6V25QcTVZVCtibnd3RFFZSktvWklodmNOQVFFTEJRQXcKSERFYU1CZ0dBMVVFQ2hNUmF6aHpMbU5zZFhOMFpYSXViRzlqWVd3d0hoY05NVGd4TVRJd01UUXdOakF6V2hjTgpNVGt4TVRJd01UUXdOakF6V2pBY01Sb3dHQVlEVlFRS0V4RnJPSE11WTJ4MWMzUmxjaTVzYjJOaGJEQ0NBU0l3CkRRWUpLb1pJaHZjTkFRRUJCUUFEZ2dFUEFEQ0NBUW9DZ2dFQkFMd05HZGRHM3psTWJ3NlNkQUVXOUw5VnlxUU0KbVBjZUVVK2FZL3lZS3ZnVnFVMGVHaWl2bkIzb05tbFpUUDRhZU1mOTdCWjUwRTFIeWxTeE82L21rY2YycWVvcwp0b0d6TkV3VktoTC9oY3JXV2d1L0cwNWg5SCtTSlJQcThIRVNKNTV4K0NvSXBoNzlKZm12NVoyTE1Zc0ZSaC95CkNaZVNOREx6N2E1K0lud2Z4VEVoRjllWUIwdVVpWjlrRmZXUUt6dW50d2NUN1g0OWxYUng3eTQ3ZzBkQ0FtdlgKYXNqUDl1bkpSLzFVVDArRWkwQmtPWFM0NUg1NXl6NkpiZUZva2ViVEljdTd6Zk1yL3NtaXhjenNlMXFsSDQwSwpYYjcyTUhuRnlCcmpNK2VyckduMWVxY3ZzS2FsUDQzQnozN3c3R014bExha0ZXdU1IV2JSRVNQSXVNTUNBd0VBCkFhTWpNQ0V3RGdZRFZSMFBBUUgvQkFRREFnSUVNQThHQTFVZEV3RUIvd1FGTUFNQkFmOHdEUVlKS29aSWh2Y04KQVFFTEJRQURnZ0VCQUhlV3pWUmJYZ1owTVdleG5GQ2tZRjREY0RuOWlFck5kWDNEZXlwR1BYLy9JcG1VaXhIVgp4K0tpN2plbjAydUR2VzAwS05PcE1Wdk5FRjBNMkdrbElCRUI1RHFuYkc2MktoUng1NXdtREd4TVVyM3ZsaDVxCjJpUnBIYmltSFlEZlhaQ1ptNXNmVGJBMFNZazdVeS9HRDVEVFdGaDZlZTVZNDFYVG1IS2k1TFVEMW1COFVmaVgKWHBDT01MNWpibm1hZ08yTXdDcGlCN29CQy9yOEVNY3BqUHJjNnU1WWVhTWFiU1JrREhNZ25IUldwNzFLdDdWMApwM1VhS0NjYzFtekROTkpRWmpQTW1VZk1nQWgvcHJMRzlBdG5KbzBiQnZSK1F3TnViZDdldU92b2x6NytRanNjCk43YWYzS2p2clM2V1YwUkFvZGJvcnd2Si9rbDlPcnJYdlBJPQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg==
service:
name: istio-galley
namespace: istio-system
path: /admitmixer
failurePolicy: Fail
name: mixer.validation.istio.io
namespaceSelector: {}
rules:

apiGroups:

config.istio.io
apiVersions:
v1alpha2
operations:
CREATE
UPDATE
resources:
rules
attributemanifests
circonuses
deniers
fluentds
kubernetesenvs
listcheckers
memquotas
noops
opas
prometheuses
rbacs
servicecontrols
solarwindses
stackdrivers
cloudwatches
dogstatsds
statsds
stdios
apikeys
authorizations
checknothings
listentries
logentries
metrics
quotas
reportnothings
servicecontrolreports
tracespans

2018-11-21T08:14:21.936806Z     warn    istio-galley validatingwebhookconfiguration update deferred: istio-system/istio-galley endpoint not ready: no ready addresses

Can you check the endpoint after you delete the pod and the new pod is running again? Also, can you check the logs after you verify that the new pod/endpoint are up and running? Can you also do kubectl -n istio-system describe pod <istio-galley-pod-name> after the new pod is created to see if the readiness probe is intermediately failing?

@ayj
[root@k8s-master1 ~]# kubectl -n istio-system describe pod istio-galley-58f566cb66-2kt8r
Name:               istio-galley-58f566cb66-2kt8r
Namespace:          istio-system
Priority:           0
PriorityClassName:
Node:               k8s-node1/10.117.150.34
Start Time:         Wed, 21 Nov 2018 16:14:16 +0800
Labels:             istio=galley
pod-template-hash=1491227622
Annotations:        scheduler.alpha.kubernetes.io/critical-pod=
sidecar.istio.io/inject=false
Status:             Running
IP:                 192.168.36.110
Controlled By:      ReplicaSet/istio-galley-58f566cb66
Containers:
validator:
Container ID:  docker://a1c3171a094ed17095d633c818dc697ec69af4962cbf690315c6e875865ea757
Image:         docker.io/istio/galley:1.0.3
Image ID:      docker-pullable://istio/galley@sha256:cffec029bf2a1b16a3bd2aa1a1c309f5fd5c686e89edbcabcebea6ff1c737ed0
Ports:         443/TCP, 9093/TCP
Host Ports:    0/TCP, 0/TCP
Command:
/usr/local/bin/galley
validator
--deployment-namespace=istio-system
--caCertFile=/etc/istio/certs/root-cert.pem
--tlsCertFile=/etc/istio/certs/cert-chain.pem
--tlsKeyFile=/etc/istio/certs/key.pem
--healthCheckInterval=1s
--healthCheckFile=/health
--webhook-config-file
/etc/istio/config/validatingwebhookconfiguration.yaml
State:          Running
Started:      Wed, 21 Nov 2018 16:14:16 +0800
Ready:          True
Restart Count:  0
Requests:
cpu:        10m
Liveness:     exec [/usr/local/bin/galley probe --probe-path=/health --interval=10s] delay=5s timeout=1s period=5s #success=1 #failure=3
Readiness:    exec [/usr/local/bin/galley probe --probe-path=/health --interval=10s] delay=5s timeout=1s period=5s #success=1 #failure=3
Environment:
Mounts:
/etc/istio/certs from certs (ro)
/etc/istio/config from config (ro)
/var/run/secrets/kubernetes.io/serviceaccount from istio-galley-service-account-token-pr8vs (ro)
Conditions:
Type              Status
Initialized       True
Ready             True
ContainersReady   True
PodScheduled      True
Volumes:
certs:
Type:        Secret (a volume populated by a Secret)
SecretName:  istio.istio-galley-service-account
Optional:    false
config:
Type:      ConfigMap (a volume populated by a ConfigMap)
Name:      istio-galley-configuration
Optional:  false
istio-galley-service-account-token-pr8vs:
Type:        Secret (a volume populated by a Secret)
SecretName:  istio-galley-service-account-token-pr8vs
Optional:    false
QoS Class:       Burstable
Node-Selectors:
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type    Reason     Age   From                Message

Normal  Scheduled  17h   default-scheduler   Successfully assigned istio-system/istio-galley-58f566cb66-2kt8r to k8s-node1
Normal  Pulled     17h   kubelet, k8s-node1  Container image "docker.io/istio/galley:1.0.3" already present on machine
Normal  Created    17h   kubelet, k8s-node1  Created container
Normal  Started    17h   kubelet, k8s-node1  Started container

Your format is so difficult to read.

authors: Linuxbody ayj hzxuzhonghu


text:
Add '.vscode' directory to ignored files

What this PR does / why we need it:
With Goland likely become paid license by end of year, expect more users to use free vscode
Which issue this PR fixes: fixes #1541
Special notes for your reviewer:
Ignores entire vscode directory, could allow sharing of setting files (e.g., .vscode/settings.json, .vscode/extensions.json), but these are also ignored for now.
Release note:
NONE

@elevran: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
0fef2acba1277f44b0eba1fcb3680c56fa1ed7f6
link
/test istio-presubmit

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.

Funny. prow tests fail for addition to .gitignore.

/retest

@elevran: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
0a1b621035e89f09f83a072692a2b343968de6fd
link
/test istio-presubmit

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.

force merging as this is just an update to .gitignore. Prow is broken

source: gharchive/pull-request

authors: elevran istio-testing rshriram

repo: istio/istio

license_type: permissive

license_source: github-api


text:
fix a typo

Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

🤔 🐛 You appear to be fixing a bug in Go code, yet your PR doesn't include updates to any test files. Did you forget to add a test?
Courtesy of your friendly test nag.

Hi @waret. Thanks for your PR.
I'm waiting for a istio 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.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: waret
To complete the pull request process, please assign costinm
You can assign the PR to them by writing /assign @costinm 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:

pilot/OWNERS

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

/ok-to-test
/lgtm
/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: howardjohn, waret
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:

pilot/OWNERS [howardjohn]

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

@waret: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/racetest.sh
f5c000e5f5b9009bf7bcb2aa575628b155d1df3e
link
/test istio-racetest-master

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.

/retest

@waret: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/racetest.sh
f5c000e5f5b9009bf7bcb2aa575628b155d1df3e
link
/test istio-racetest-master

prow/integ-istioctl-k8s-presubmit-tests.sh
f5c000e5f5b9009bf7bcb2aa575628b155d1df3e
link
/test integ-istioctl-k8s-presubmit-tests-master

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.

@waret: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/racetest.sh
f5c000e5f5b9009bf7bcb2aa575628b155d1df3e
link
/test istio-racetest-master

prow/integ-istioctl-k8s-presubmit-tests.sh
f5c000e5f5b9009bf7bcb2aa575628b155d1df3e
link
/test integ-istioctl-k8s-presubmit-tests-master

prow/istio-pilot-multicluster-e2e.sh
f5c000e5f5b9009bf7bcb2aa575628b155d1df3e
link
/test istio-pilot-multicluster-e2e-master

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.

@waret: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/racetest.sh
f5c000e5f5b9009bf7bcb2aa575628b155d1df3e
link
/test istio-racetest-master

prow/integ-istioctl-k8s-presubmit-tests.sh
f5c000e5f5b9009bf7bcb2aa575628b155d1df3e
link
/test integ-istioctl-k8s-presubmit-tests-master

prow/istio-pilot-multicluster-e2e.sh
f5c000e5f5b9009bf7bcb2aa575628b155d1df3e
link
/test istio-pilot-multicluster-e2e-master

prow/integ-mixer-k8s-presubmit-tests.sh
f5c000e5f5b9009bf7bcb2aa575628b155d1df3e
link
/test integ-mixer-k8s-presubmit-tests-master

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.

authors: howardjohn istio-testing waret


text:
[DO NOT MERGE] Auto PR to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
5aefa764f70bfdc72ea2c59437e3a5c33e5328e8
link
/test istio-pilot-e2e

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.


text:
match istio.io/rev=default label when revision is not set

See #23319
The goal here is to also support matching istio.io/rev=default when revision is not set. This has some minor improvements by having a consistent label used throughout. This makes docs/UX a bit simpler. It also means to switch from default to revision you just overwrite a label instead of kubectl label ns istio-injection- istio.io/rev=foo
This is challenging because the k8s api does not support the label
selector istio-injection=enabled || istio.io/rev=default, we can only
AND them together. To get around this, we make two webhooks (in one
resource). This requires a minor patch to the patching logic

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

Test name
Commit
Details
Rerun command

lint_istio
50a8ef862d944fcd40d0bd5f528645102355e17e
link
/test lint_istio

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.

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

Test name
Commit
Details
Rerun command

lint_istio
0e4a3ca3ea465578db79173b6853eef1dd5acc18
link
/test lint_istio

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.

@esnible the other changes are just testing, and changing the webhook cert patching to support multiple webhooks - today it looks only at [0]

@costinm this is intended for 1.6. Sorry I had no description in the PR, I split this off from another PR that had one. The goal here is to also support matching istio.io/rev=default when revision is not set. This has some minor improvements by having a consistent label used throughout. This makes docs/UX a bit simpler. It also means to switch from default to revision you just overwrite a label instead of kubectl label ns istio-injection- istio.io/rev=foo.
The benefit is not huge - I was on the fence if we should do this. If you think its too complex I would agree, I am pretty much neutral.

I'm not sure either. Ideally we should minimize disruption - if users have istio-inject: true, no reason for them to change. It's as good as istio.io/rev:default IMO.
I like the split to 2 webhooks - one for explicit istio.io/rev match, and one that is only added for the 'default' install - which may also catch wildcard.
The future also seems relatively clear: if we move ahead with Lin's changes and MC, we'll need to have a singleton (which can be the default) that splits to different control planes. At that point we'll have more options - including pod labels/annotations. And we could switch back to 'match everything by default' - and let default istiod sort it out.  In other words - I don't know if current state is the final state, so less motivation to churn istio-inject.

@costinm agreed that either way we should merge this in some form. So I guess the question is do we want the istio.io/rev webhook only when they are actually using a revision or also set it up for default

We need a go/no-go decision for this because so I can create a PR for the analyzer.  https://github.com/istio/istio/issues/23319

authors: costinm esnible howardjohn istio-testing


text:
proxyv2 - update Dockerfile to use distroless multi-arch image

Addresses #26652 by using a multi-arch Distroless image for proxyv2 and making the COPY architecture agnostic.
This PR replaces https://github.com/istio/istio/pull/27700, which was closed due to a bad re-base from master when trying to fix a failing integ-distroless-k8s-tests_istio test.
This change builds/tests locally, however it fails Prow with the error iptables-restore v1.6.1: unknown option "--dport". See https://github.com/istio/istio/pull/27700#issuecomment-703020915 for more information.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[X] Test and Release
[ ] User Experience
[X] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[X] Does not have any changes that may affect Istio users.

Hi @ecliptik. Thanks for your PR.
I'm waiting for a istio 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.

/ok-to-test

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

Test name
Commit
Details
Rerun command

release-notes_istio
d2d9df63475bb7766e8abc8bd59ea8bb51e3c32d
link
/test release-notes_istio

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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
d2d9df63475bb7766e8abc8bd59ea8bb51e3c32d
link
/test release-notes_istio

integ-distroless-k8s-tests_istio
d2d9df63475bb7766e8abc8bd59ea8bb51e3c32d
link
/test integ-distroless-k8s-tests_istio

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.

LGTM if we can figure out how to get the test passing

@ecliptik: PR needs rebase.

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.

authors: ecliptik howardjohn istio-testing


text:
Automator: update istio/api@release-1.10 dependency in istio/istio@release-1.10

Generated by Automator - 2021-04-20T15:33:46+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio_release-1.10
2939069e28f36db225c6df6c3243f711a5fb67f8
link
/test integ-telemetry-mc-k8s-tests_istio_release-1.10

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.

/retest

authors: Monkeyanator istio-testing


text:
Test envoy update

Please provide a description of this PR:
Test for pulling in latest Envoy. Comment of change needed here: https://github.com/istio/istio/pull/38310#issuecomment-1094511914
Run update-reps.sh script to get latest dependencies including Envoy.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test unit-tests_istio

integ-helm_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-helm_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test unit-tests_istio

integ-helm_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-helm_istio

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test unit-tests_istio

integ-helm_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-helm_istio

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-ipv6_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-ipv6_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test unit-tests_istio

integ-helm_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-helm_istio

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-ipv6_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-ipv6_istio

integ-pilot-istiodremote_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test unit-tests_istio

integ-helm_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-helm_istio

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-ipv6_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-ipv6_istio

integ-pilot-istiodremote_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-istiodremote-mc_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote-mc_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test unit-tests_istio

integ-helm_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-helm_istio

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-ipv6_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-ipv6_istio

integ-pilot-istiodremote_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-istiodremote-mc_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot-multicluster_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-multicluster_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test unit-tests_istio

integ-helm_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-helm_istio

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-ipv6_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-ipv6_istio

integ-pilot-istiodremote_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-istiodremote-mc_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot-multicluster_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-multicluster_istio

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

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.

@ericvn: PR needs rebase.

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-helm_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-helm_istio

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-ipv6_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-ipv6_istio

integ-pilot-istiodremote_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-istiodremote-mc_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot-multicluster_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-multicluster_istio

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-helm_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-helm_istio

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-ipv6_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-ipv6_istio

integ-pilot-istiodremote_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-istiodremote-mc_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot-multicluster_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-multicluster_istio

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-helm_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-helm_istio

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-ipv6_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-ipv6_istio

integ-pilot-istiodremote_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-istiodremote-mc_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot-multicluster_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-multicluster_istio

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-helm_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-helm_istio

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-pilot-istiodremote_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-istiodremote-mc_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot-multicluster_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-multicluster_istio

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

integ-ipv6_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-ipv6_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-helm_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-helm_istio

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-pilot-istiodremote_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-istiodremote-mc_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote-mc_istio

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

integ-ipv6_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-ipv6_istio

integ-pilot-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-multicluster_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-pilot-istiodremote_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-istiodremote-mc_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote-mc_istio

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

integ-ipv6_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-ipv6_istio

integ-pilot-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-multicluster_istio

integ-helm_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-helm_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-pilot-istiodremote-mc_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote-mc_istio

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

integ-ipv6_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-ipv6_istio

integ-pilot-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-multicluster_istio

integ-helm_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-helm_istio

integ-pilot-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-pilot-istiodremote-mc_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote-mc_istio

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

integ-ipv6_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-ipv6_istio

integ-pilot-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-multicluster_istio

integ-helm_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-helm_istio

integ-pilot-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote_istio

integ-telemetry-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-mc_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-pilot-istiodremote-mc_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote-mc_istio

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

integ-ipv6_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-ipv6_istio

integ-pilot-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-multicluster_istio

integ-helm_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-helm_istio

integ-pilot-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote_istio

integ-telemetry-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-mc_istio

integ-pilot_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-pilot-istiodremote-mc_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote-mc_istio

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

integ-ipv6_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-ipv6_istio

integ-pilot-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-multicluster_istio

integ-helm_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-helm_istio

integ-pilot-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote_istio

integ-telemetry-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-mc_istio

integ-pilot_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot_istio

analyze-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test analyze-tests_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-pilot-istiodremote-mc_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-pilot-istiodremote-mc_istio

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

integ-ipv6_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-ipv6_istio

integ-pilot-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-multicluster_istio

integ-helm_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-helm_istio

integ-pilot-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote_istio

integ-telemetry-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-mc_istio

integ-pilot_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot_istio

analyze-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test analyze-tests_istio

lint_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test lint_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

integ-ipv6_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-ipv6_istio

integ-pilot-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-multicluster_istio

integ-helm_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-helm_istio

integ-pilot-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote_istio

integ-telemetry-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-mc_istio

integ-pilot_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot_istio

analyze-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test analyze-tests_istio

lint_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test lint_istio

integ-pilot-istiodremote-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote-mc_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

integ-ipv6_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-ipv6_istio

integ-pilot-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-multicluster_istio

integ-helm_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-helm_istio

integ-pilot-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote_istio

integ-telemetry-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-mc_istio

integ-pilot_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot_istio

analyze-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test analyze-tests_istio

lint_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test lint_istio

integ-pilot-istiodremote-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote-mc_istio

integ-security_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

integ-ipv6_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-ipv6_istio

integ-pilot-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-multicluster_istio

integ-helm_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-helm_istio

integ-pilot-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote_istio

integ-telemetry-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-mc_istio

integ-pilot_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot_istio

analyze-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test analyze-tests_istio

lint_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test lint_istio

integ-pilot-istiodremote-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote-mc_istio

integ-security_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security_istio

integ-security-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security-istiodremote_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

integ-ipv6_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-ipv6_istio

integ-pilot-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-multicluster_istio

integ-helm_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-helm_istio

integ-pilot-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote_istio

integ-telemetry-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-mc_istio

integ-pilot_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot_istio

analyze-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test analyze-tests_istio

lint_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test lint_istio

integ-pilot-istiodremote-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote-mc_istio

integ-security_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security_istio

integ-security-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security-istiodremote_istio

integ-security-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security-multicluster_istio

gencheck_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test gencheck_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-distroless_istio

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

integ-ipv6_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-ipv6_istio

integ-pilot-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-multicluster_istio

integ-helm_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-helm_istio

integ-pilot-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote_istio

integ-telemetry-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-mc_istio

integ-pilot_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot_istio

analyze-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test analyze-tests_istio

lint_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test lint_istio

integ-pilot-istiodremote-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote-mc_istio

integ-security_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security_istio

integ-security-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security-istiodremote_istio

integ-security-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security-multicluster_istio

gencheck_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test gencheck_istio

integ-telemetry_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

integ-ipv6_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-ipv6_istio

integ-pilot-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-multicluster_istio

integ-helm_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-helm_istio

integ-pilot-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote_istio

integ-telemetry-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-mc_istio

integ-pilot_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot_istio

analyze-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test analyze-tests_istio

lint_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test lint_istio

integ-pilot-istiodremote-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote-mc_istio

integ-security_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security_istio

integ-security-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security-istiodremote_istio

integ-security-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security-multicluster_istio

gencheck_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test gencheck_istio

integ-telemetry_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry_istio

integ-distroless_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-distroless_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-operator-controller_istio
f996329d82b5d3e6674f9fac93fa91745b7c0223
link
true
/test integ-operator-controller_istio

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

integ-ipv6_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-ipv6_istio

integ-pilot-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-multicluster_istio

integ-helm_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-helm_istio

integ-pilot-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote_istio

integ-telemetry-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-mc_istio

integ-pilot_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot_istio

analyze-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test analyze-tests_istio

lint_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test lint_istio

integ-pilot-istiodremote-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote-mc_istio

integ-security_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security_istio

integ-security-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security-istiodremote_istio

integ-security-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security-multicluster_istio

gencheck_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test gencheck_istio

integ-telemetry_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry_istio

integ-distroless_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-distroless_istio

integ-telemetry-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-istiodremote_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

integ-ipv6_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-ipv6_istio

integ-pilot-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-multicluster_istio

integ-helm_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-helm_istio

integ-pilot-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote_istio

integ-telemetry-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-mc_istio

integ-pilot_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot_istio

analyze-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test analyze-tests_istio

lint_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test lint_istio

integ-pilot-istiodremote-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote-mc_istio

integ-security_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security_istio

integ-security-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security-istiodremote_istio

integ-security-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security-multicluster_istio

gencheck_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test gencheck_istio

integ-telemetry_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry_istio

integ-distroless_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-distroless_istio

integ-telemetry-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-istiodremote_istio

integ-operator-controller_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-operator-controller_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test unit-tests_istio

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

integ-ipv6_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-ipv6_istio

integ-pilot-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-multicluster_istio

integ-helm_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-helm_istio

integ-pilot-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote_istio

integ-telemetry-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-mc_istio

integ-pilot_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot_istio

analyze-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test analyze-tests_istio

lint_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test lint_istio

integ-pilot-istiodremote-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote-mc_istio

integ-security_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security_istio

integ-security-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security-istiodremote_istio

integ-security-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security-multicluster_istio

gencheck_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test gencheck_istio

integ-telemetry_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry_istio

integ-distroless_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-distroless_istio

integ-telemetry-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-istiodremote_istio

integ-operator-controller_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-operator-controller_istio

release-notes_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-notes_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-test_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test release-test_istio

integ-cni_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-cni_istio

integ-ipv6_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-ipv6_istio

integ-pilot-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-multicluster_istio

integ-helm_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-helm_istio

integ-pilot-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote_istio

integ-telemetry-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-mc_istio

integ-pilot_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot_istio

analyze-tests_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test analyze-tests_istio

lint_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test lint_istio

integ-pilot-istiodremote-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-pilot-istiodremote-mc_istio

integ-security_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security_istio

integ-security-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security-istiodremote_istio

integ-security-multicluster_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-security-multicluster_istio

integ-telemetry_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry_istio

integ-distroless_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-distroless_istio

integ-telemetry-istiodremote_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-istiodremote_istio

integ-operator-controller_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-operator-controller_istio

unit-tests_istio
a6484bd9619beac898d3062f513692ed184425ae
link
true
/test unit-tests_istio

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.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc_istio
55d22b5388f7176814e182d6030f7a736ebccea5
link
true
/test integ-telemetry-mc_istio

unit-tests_istio
e3f3fa59c73c94efce4b3ce50a74018f5855807b
link
true
/test unit-tests_istio

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.

Updated the Goldens and making it further. Seem to have an issue with Envoy starting?
Didn't find a registered implementation for 'envoy.filters.http.router' with type URL: ''
2022-04-11T22:09:27.087095Z	info	Envoy 'envoy' (epoch 0) exited with error: exit status 1
2022-04-11T22:09:27.087357Z	info	Failed freeing BaseID for Envoy 'envoy' (epoch 0): error deleting Envoy base ID 63631 shared memory /dev/shm/envoy_shared_memory_63631: remove /dev/shm/envoy_shared_memory_63631: no such file or directory
    instance_test.go:328: exit status 1

@ericvn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
5ccc8cc74293aee10d4b5f9f87f9ad9416079cfe
link
true
/test unit-tests_istio

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.

I'm not sure of the best way to try and get logs when running the unit-tests to see what might be wrong.

@ericvn: PR needs rebase.

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.

Added in  changes from @howardjohn

authors: ericvn istio-testing


text:
refactor constants

Please provide a description of this PR:
refactor constants to one place

@zirain: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
a28a08e0af07d12ac6f31c4393046562ff78a7f7
link
true
/test lint_istio

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.

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
a28a08e0af07d12ac6f31c4393046562ff78a7f7
link
true
/test lint_istio

unit-tests_istio
a28a08e0af07d12ac6f31c4393046562ff78a7f7
link
true
/test unit-tests_istio

gencheck_istio
a28a08e0af07d12ac6f31c4393046562ff78a7f7
link
true
/test gencheck_istio

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.

@zirain: PR needs rebase.

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.

@zirain: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
eca75a879564fe0df26604492648f9dca59bd249
link
true
/test integ-distroless_istio

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.

/test integ-distroless_istio

authors: istio-testing zirain


text:
ambient: test cross-waypoint load balancing

This is currently broken

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

authors: howardjohn istio-testing


text:
Bug fix and perf improvements.

Use a buffer pool when computing signatures in runtime/handler

Fix a bug in protobuf yaml code where it was using a byte[] from a pooled buffer
even after having put the buffer back into a pool, leading to racy behavior.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
If they are not already assigned, you can assign the PR to them by writing /assign @geeknoid in a comment when ready.
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:

mixer/OWNERS

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

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
4e773b95fb060cf9f4d6fd57bdc2cb8111d631d1
link
/test istio-unit-tests

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.

/test istio-unit-tests

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
4e773b95fb060cf9f4d6fd57bdc2cb8111d631d1
link
/test istio-unit-tests

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.

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
414a5ef5565b60161d5a12d1f75d8c77692f26e3
link
/test istio-unit-tests

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.

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
1cbb75f380a9c7bf88b3a46e78ce4014ea0c31b4
link
/test istio-unit-tests

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.

@geeknoid why was this closed?

authors: geeknoid istio-testing mandarjog


text:
coverage improvement for istio.io/istio/pilot/pkg/model

xref #8568
before change:
istio.io/istio/pilot/pkg/model/authorization.go:51:	addServiceRole				0.0%
istio.io/istio/pilot/pkg/model/authorization.go:68:	addServiceRoleBinding			0.0%
istio.io/istio/pilot/pkg/model/authorization.go:96:	AddConfig				0.0%
istio.io/istio/pilot/pkg/model/authorization.go:112:	RolesForNamespace			0.0%
istio.io/istio/pilot/pkg/model/authorization.go:126:	RoleToBindingsForNamespace		0.0%
istio.io/istio/pilot/pkg/model/authorization.go:140:	newAuthzPolicies			0.0%
...
istio.io/istio/pilot/pkg/model/config.go:565:		ServiceEntries				0.0%
istio.io/istio/pilot/pkg/model/config.go:574:		sortConfigByCreationTime		0.0%
istio.io/istio/pilot/pkg/model/config.go:604:		EnvoyFilter				0.0%
istio.io/istio/pilot/pkg/model/config.go:635:		HTTPAPISpecByDestination		0.0%

and coverage of this package is
coverage: 66.70% of statements

But after change
istio.io/istio/pilot/pkg/model/authorization.go:51:	addServiceRole				87.5%
istio.io/istio/pilot/pkg/model/authorization.go:68:	addServiceRoleBinding			92.9%
istio.io/istio/pilot/pkg/model/authorization.go:96:	AddConfig				83.3%
istio.io/istio/pilot/pkg/model/authorization.go:112:	RolesForNamespace			100.0%
istio.io/istio/pilot/pkg/model/authorization.go:126:	RoleToBindingsForNamespace		100.0%
....
istio.io/istio/pilot/pkg/model/config.go:565:		ServiceEntries				75.0%
istio.io/istio/pilot/pkg/model/config.go:574:		sortConfigByCreationTime		66.7%
istio.io/istio/pilot/pkg/model/config.go:604:		EnvoyFilter				71.4%
istio.io/istio/pilot/pkg/model/config.go:635:		HTTPAPISpecByDestination		91.7%

and coverage of this package is
coverage: 71.3% of statements

greater than 70% defined in https://github.com/istio/istio/blob/master/codecov.requirement

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: rshriram
If they are not already assigned, you can assign the PR to them by writing /assign @rshriram in a comment when ready.
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:

pilot/OWNERS

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

Hi @stewart-yu. Thanks for your PR.
I'm waiting for a istio 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.
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.

/ok-to-test

@stewart-yu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
f185feac2f95c17044a22d19bb6be2398e335154
link
/test istio-unit-tests

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.

/assign @geeknoid @ayj

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ayj
If they are not already assigned, you can assign the PR to them by writing /assign @ayj in a comment when ready.
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:

pilot/OWNERS

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

@stewart-yu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
fa56255bb8ac6388e791ea88cef8a1c0d4dc5cb8
link
/test istio-pilot-multicluster-e2e

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.

/test istio-pilot-multicluster-e2e

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rshriram
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:

pilot/OWNERS [rshriram]

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

authors: hzxuzhonghu istio-testing stewart-yu


text:
Define PROXY_TAG in istio.VERSION

This is required to automate release now that proxy is part the release artifacts.
Release note:

None

/assign @sebastienvas
/assign @ldemailly

PTAL

@chxchx Could you resolve your conficts ?

side note: there is no real value in using the -flags in updateVersion, it's much simpler to edit istio.VERSION first and then run it with no flag
maybe we can just get rid of all those flags (in 0.3)

poking submit queue

authors: chxchx ldemailly sebastienvas


text:
[DO NOT MERGE] Auto PR to update dependencies of old_pilot_repo

This PR will be merged automatically once checks are successful.
none

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
b571a469120cc1325e0bf59fc0341621edd34aa8
link
/test pilot-presubmit

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.

license_source: bigquery


text:
sendImageToAppGroups crashes when sending same image

I want to create 3 activities with the same icon (icon.png). When the plugin creates 3rd of them it removes a file used for the 2nd - 76th number of lines in app_groups_image_service.dart. Deleting this line helps, however, it's a workaround.

The error still occurs. Removing this line helps, however, there should be a way to handle the image with the same name. Script shouldn't remove it if it's used by another live activity.
file.deleteSync(); in app_groups_image_service.dart:76

source: gharchive/issue

license: MIT