envoyproxy

EnvoyFilter filter for grpc_json_transcoder in istio

由 a 夏天 提交于 2020-01-14 05:36:26
问题 istio EnvoyFilter is not converting http1X to http2X(GRPXC) service I gave GRP Service in Azure AKS and istio-1.1.6 my GRPC service is listening 50051 port , I have EnvoyFilter filter for trascoding of JSON to GRPC but on my service I am still getting http 1X request even I am calling it through GRPC Client (Http2.o) request Envoy Filer apiVersion: networking.istio.io/v1alpha3 kind: EnvoyFilter metadata: name: envoy-proxy namespace: istio-system spec: filters: - listenerMatch: listenerType:

Istio distributed tracing with Jaeger not working

由 筅森魡賤 提交于 2020-01-02 08:24:17
问题 I'm trying to set up a local k8s cluster and on minikube with installed istio and I have an issue with enabling distributed tracing with Jaeger. I have 3 microservices A -> B -> C . I am propagating the all the headers that are needed: {"x-request-id", "x-b3-traceid", "x-b3-spanid", "x-b3-parentspanid", "x-b3-sampled", "x-b3-flags", "x-ot-span-context"} But on Jaeger interface, I can only see the request to the service A and I cannot see the request going to service B. I have logged the

Docker installed python 3.5.2 instead of python 3.6

由 笑着哭i 提交于 2019-12-13 19:18:47
问题 I don't get it why python 3.5.2 is installed and not python 3.6 . So I cannot execute my python file because I use f string literal syntax which is only available in python 3.6 . Maybe someone can help me? FROM envoyproxy/envoy:latest RUN apt-get update && apt-get -q install -y \ curl \ software-properties-common \ python-software-properties RUN add-apt-repository ppa:deadsnakes/ppa RUN apt-get update && apt-get -q install -y \ python3.6 \ python3-pip RUN python3.6 --version && pip3 --version

Accessing service using istio ingress gives 503 error when mTLS is enabled

由 独自空忆成欢 提交于 2019-12-12 08:14:55
问题 I have a mutual TLS enabled Istio mesh. My setup is as follows A service running inside a pod (Service container + envoy) An envoy gateway which stays in front of the above service. An Istio Gateway and Virtual Service attached to this. It routes /info/ route to the above service. Another Istio Gateway configured for ingress using the default istio ingress pod. This also has Gateway+Virtual Service combination. The virtual service directs /info/ path to the service described in 2 I'm

Envoy Pod to Pod communication within a Service in K8

由 萝らか妹 提交于 2019-12-11 17:41:59
问题 Is it possible to send a http Rest request to another K8 Pod that belongs to the same Service in Kubernetes when Envoy is configured? Important : I have another question here that directed me to ask with Envoy specific tags. E. G. Service name = UserService , 2 Pods (replica = 2) Pod 1 --> Pod 2 //using pod ip not load balanced hostname Pod 2 --> Pod 1 The connection is over Rest GET 1.2.3.4:7079/user/1 The value for host + port is taken from kubectl get ep Both of the pod IP's work

Istio envoy is dropping requests with Host header

由 梦想的初衷 提交于 2019-12-10 17:04:34
问题 I having an issue trying to get Istio working on my cluster. My infrastructure looks like this: I have a Magento Store with a varnish as front cache. It was working before istio installation. I have already enabled envoy injection. Varnish is deployed in a pod and has its own service redirects uncached to magento service. The problem comes when I try to curl from varnish to magento. If I curl magento service from varnish I get a redirect to magento URL (which is the expected behavior) root

Istio distributed tracing with Jaeger not working

由 邮差的信 提交于 2019-12-06 03:19:04
I'm trying to set up a local k8s cluster and on minikube with installed istio and I have an issue with enabling distributed tracing with Jaeger. I have 3 microservices A -> B -> C . I am propagating the all the headers that are needed: {"x-request-id", "x-b3-traceid", "x-b3-spanid", "x-b3-parentspanid", "x-b3-sampled", "x-b3-flags", "x-ot-span-context"} But on Jaeger interface, I can only see the request to the service A and I cannot see the request going to service B. I have logged the headers that are sent in the request. Headers from service A: Header - x-request-id: c2804368-2ff0-9d90-a2aa
订阅 envoyproxy