Ric Hincapie

Results 9 comments of Ric Hincapie

> Hi all, Are any of you still hitting this issue? I've not been able to reproduce anything similar. I got the same working with Kubernetes 1.19, Istio 1.9.9: `ERRO[0005]...

There's also an issue regarding lack of clarity about the need to create WorkloadEntry and ServiceEntry if user is not onboarded in the yet experimental `automated workload entry`

This is a QA cluster where a virtual division of different versioned and parallel CP was required by the platform team. Not having the full motives, the reasons for this...

Ok. Is it worth documenting this limitation here? https://istio.io/latest/docs/reference/config/istio.mesh.v1alpha1/ I could do it.

@elviskahoro wdyt?

the `imagePullSecret` implementation for istiod is at its ServiceAcount level [here](https://github.com/istio/istio/blob/1c5963301ae491bdb7a76d9480fcc0610c045559/manifests/charts/istio-control/istio-discovery/templates/serviceaccount.yaml#L4). From Kubernetes [docs](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#verify-that-imagepullsecrets-are-set-for-new-pods): > Now, when a new Pod is created in the current namespace and using the default...

This is creating issues with Istio's mesh-onboarded VMs. VMs in Istio work different that pods, because the sidecar agent uses K8s provided SA token only to onboard into the mesh,...