Hi Stefan,

While working on an out of process adapter I noticed that the "Dispatch Count By Handler" and "Dispatch Duration By Handler" graphs were producing graphs with "No Data Points" text. Screenshot added.

I took a look at the query and was able to obtain those data points directly from Prometheus. It appears the get request to obtain the data from Grafana has added escaped characters to a handler name with the format x.y.z. These in turn are being URL encoded meaning the query is incorrect. Will add a fix in PR.

Hi,

With the latest istio

follow https://github.com/stefanprodan/istio-gke/blob/master/docs/istio/04-istio-setup.md

we're receiving this error

Error: validation failed: unable to recognize "": no matches for kind "ClusterIssuer" in version "certmanager.k8s.io/v1alpha1"

after manage to install cert-manager, at step expose service grafana

https://github.com/stefanprodan/istio-gke/blob/master/docs/istio/06-grafana-config.md

when access grafana there is an error

upstream connect error or disconnect/reset before headers. reset reason: connection failure

Can help review the installation and setup step. thanks!

The last commit changed the NATS MTLS exclusion to the following:

apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
    name: "nats-no-mtls"
    namespace: {{ .Release.Namespace }}
spec:
    host: "nats.openfaas.svc.cluster.local"
    trafficPolicy:
        tls:
            mode: DISABLE

The template in the namespace causes the apply to fail in a cluster freshly set up following all the steps here.

I have been able to fix this by using the namespace "openfaas", as was used before.

Hi Stefan

I hope you could answer my question. It is not directly an issue with your repository, but im following a lot of your guides and need some help >.<

If i have a service in the default namespace that wants to reach a service in another namespace.. i use <name>.<namespace>.svc.cluster.local
but if i wanna split that traffic between two services using weight: i have the following VS in the default namespace:

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: backend
  namespace: default
spec:
  hosts:
  - backend
  http:
  - route:
    - destination:
        host: backend.mynamespace.svc.cluster.local
      weight: 50
  - route:
    - destination:
        host: backend-management.mynamespace.svc.cluster.local
      weight: 50

If my service in default tries to use http://backend:portto access it, it fails
I need the full http://backend.namespace.svc.cluster.local:portfor it to work, but then my traffic is not split?

What am i doing wrong?

Hi Stefan

Ive installed using 1.1.0.RC2

im unable to get the certificates working. What exactly is supposed to create istio-ingressgateway-certs secret? Im not getting one created. :/

Hi Stefan,

Just an FYI, but you'll get 1.0.3 installed from the Istio get script now over at: https://github.com/stefanprodan/istio-gke/blob/master/docs/istio/04-istio-setup.md

It'd be good if you could update the instructions but it's not too hard to figure out otherwise.

I also got this error while deploying with helm:

helm upgrade --install istio ./install/kubernetes/helm/istio --namespace=istio-system -f ./my-istio.yaml
Release "istio" does not exist. Installing it now.
Error: apiVersion "config.istio.io/v1alpha2" in istio/charts/mixer/templates/config.yaml is not available

Alex

Would it be possible to adapt the SDS feature of istio to this documentation?
A nice side-effect would be that no restart of the IngressGateway is necessary to apply newly obtained certificates from letsencrypt, I guess.
Is there any reason not to use the cert-manager option of the istio helm chart by the way?