Azure Kubernetes - Jaeger UI is not showing the Service deployed as a part of ISTIO?

Karthikeyan Vijayakumar

I have used the following configuration to setup the Istio

cat << EOF | kubectl apply -f -
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
metadata:
  namespace: istio-system
  name: istio-control-plane
spec:
  # Use the default profile as the base
  # More details at: https://istio.io/docs/setup/additional-setup/config-profiles/
  profile: default
  # Enable the addons that we will want to use
  addonComponents:
    grafana:
      enabled: true
    prometheus:
      enabled: true
    tracing:
      enabled: true
    kiali:
      enabled: true
  values:
    global:
      # Ensure that the Istio pods are only scheduled to run on Linux nodes
      defaultNodeSelector:
        beta.kubernetes.io/os: linux
    kiali:
      dashboard:
        auth:
          strategy: anonymous
  components:
    egressGateways:
    - name: istio-egressgateway
      enabled: true
EOF

and exposed the jaeger-query service as mentioned below

kubectl expose service jaeger-query  --type=LoadBalancer --name=jaeger-query-svc --namespace istio-system
kubectl get svc jaeger-query-svc -n istio-system -o json
export JAEGER_URL=$(kubectl get svc jaeger-query-svc -n istio-system  -o jsonpath="{.status.loadBalancer.ingress[0]['hostname','ip']}"):$(kubectl get svc jaeger-query-svc -n istio-system -o 'jsonpath={.spec.ports[0].port}')
echo http://${JAEGER_URL}
curl http://${JAEGER_URL}

I couldn't see the below deployed application in Jaeger

enter image description here

and have deployed the application as mentioned below

cat << EOF | kubectl apply -f -
apiVersion: apps/v1 # for versions before 1.9.0 use apps/v1beta2
kind: Deployment
metadata:
  name: nginx-deployment
  namespace: akv2k8s-test
spec:
  selector:
    matchLabels:
      app: nginx
  replicas: 1
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: stenote/nginx-hostname
        ports:
        - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: web
  namespace: akv2k8s-test
spec:
  selector:
    app: nginx
  ports:
  - protocol: TCP
    port: 80
EOF

cat <<EOF | kubectl apply -f -
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: public-gateway
  namespace: akv2k8s-test
spec:
  selector:
    istio: ingressgateway # use istio default ingress gateway
  servers:
  - port:
      number: 443
      name: https
      protocol: HTTPS
    tls:
      mode: SIMPLE
      credentialName: "${KEY_CERT2_NAME}"
    hosts:
    - web.zaalion.com
EOF


cat <<EOF | kubectl apply -f -
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: helloworld
  namespace: akv2k8s-test
spec:
  hosts:
    - web.zaalion.com
  gateways:
    - public-gateway
  http:
    - route:
      - destination:
          host: web.akv2k8s-test.svc.cluster.local
          port:
            number: 80
EOF

I could access the service as shown below

export EXTERNAL_IP=$(kubectl get svc istio-ingressgateway -n istio-system -o jsonpath='{.status.loadBalancer.ingress[0].ip}')

curl -v --resolve web.zaalion.com:443:$EXTERNAL_IP --cacert cert2.crt https://web.zaalion.com

I do know why the service is not listed in the Jaeger UI?

Jakub

According to istio documentation

To see trace data, you must send requests to your service. The number of requests depends on Istio’s sampling rate. You set this rate when you install Istio. The default sampling rate is 1%. You need to send at least 100 requests before the first trace is visible. Could you try to send at least 100 requests and check if it works?

If you wan't to change the default sampling rate then there is istio documentation about that.

Customizing Trace sampling

The sampling rate option can be used to control what percentage of requests get reported to your tracing system. This should be configured depending upon your traffic in the mesh and the amount of tracing data you want to collect. The default rate is 1%.

To modify the default random sampling to 50, add the following option to your tracing.yaml file.

apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  meshConfig:
    defaultConfig:
      tracing:
        sampling: 50

The sampling rate should be in the range of 0.0 to 100.0 with a precision of 0.01. For example, to trace 5 requests out of every 10000, use 0.05 as the value here.

この記事はインターネットから収集されたものであり、転載の際にはソースを示してください。

侵害の場合は、連絡してください[email protected]

編集
0

コメントを追加

0

関連記事

分類Dev

Azure Kubernetes-Jaeger UIは、ISTIOの一部としてデプロイされたサービスを表示していませんか?

分類Dev

Istio on Azure Governors Service?

分類Dev

Istio on Azure Container Service (AKS)

分類Dev

Connecting IIS deployed WCF service with Azure service bus

分類Dev

Istioの `DestinationRule`とKubernetesの` Service`の違いは?

分類Dev

Azure Kubernetes-Istio複数のロードバランサー?

分類Dev

Azure app service plan stopped showing monitoring info

分類Dev

Kubernetes + Docker + AWS = Azure + Service Fabricですか?

分類Dev

Azure Container Service Kubernetes Unmanaged ssh&kube tls security

分類Dev

How to test a deployed service endpoint?

分類Dev

IstioのJaegerとの統合を追跡するアンバサダー

分類Dev

Azure Kubernetes ServiceでDocker Trusted Registryを使用できますか?

分類Dev

Azure Kubernetes Service(AKS)でのDaskKubernetesのビッグデータの操作

分類Dev

NodePort は Azure Container Service (Kubernetes) で機能しますか

分類Dev

Update a part of the UI on Flutter

分類Dev

Android service not showing logs?

分類Dev

Web api working locally but not when deployed to Azure

分類Dev

wsDualHttpBinding Not Working When Deployed Under Azure

分類Dev

Allow requests to Kubernetes API from an init container with Istio CNI plugin

分類Dev

Not able to access Kubernetes Service

分類Dev

Applications starting but not showing UI

分類Dev

Azure DevOps Build Pipeline - A failed build still gets deployed to Azure

分類Dev

Is there a way to proxy calls to an ExternalName service thanks to an Istio VirtualService?

分類Dev

istio exclut le service de ext-auth

分類Dev

istio JWT authentication for single service behind ingress gateway

分類Dev

How to host multiple applications in one Istio service mesh?

分類Dev

How to use a Google Secret in a deployed Cloud Run Service (managed)?

分類Dev

Kubernetes ExternalName service not visible in DNS

分類Dev

Kubernetes MLflow Service Pod Connection

Related 関連記事

  1. 1

    Azure Kubernetes-Jaeger UIは、ISTIOの一部としてデプロイされたサービスを表示していませんか?

  2. 2

    Istio on Azure Governors Service?

  3. 3

    Istio on Azure Container Service (AKS)

  4. 4

    Connecting IIS deployed WCF service with Azure service bus

  5. 5

    Istioの `DestinationRule`とKubernetesの` Service`の違いは?

  6. 6

    Azure Kubernetes-Istio複数のロードバランサー?

  7. 7

    Azure app service plan stopped showing monitoring info

  8. 8

    Kubernetes + Docker + AWS = Azure + Service Fabricですか?

  9. 9

    Azure Container Service Kubernetes Unmanaged ssh&kube tls security

  10. 10

    How to test a deployed service endpoint?

  11. 11

    IstioのJaegerとの統合を追跡するアンバサダー

  12. 12

    Azure Kubernetes ServiceでDocker Trusted Registryを使用できますか?

  13. 13

    Azure Kubernetes Service(AKS)でのDaskKubernetesのビッグデータの操作

  14. 14

    NodePort は Azure Container Service (Kubernetes) で機能しますか

  15. 15

    Update a part of the UI on Flutter

  16. 16

    Android service not showing logs?

  17. 17

    Web api working locally but not when deployed to Azure

  18. 18

    wsDualHttpBinding Not Working When Deployed Under Azure

  19. 19

    Allow requests to Kubernetes API from an init container with Istio CNI plugin

  20. 20

    Not able to access Kubernetes Service

  21. 21

    Applications starting but not showing UI

  22. 22

    Azure DevOps Build Pipeline - A failed build still gets deployed to Azure

  23. 23

    Is there a way to proxy calls to an ExternalName service thanks to an Istio VirtualService?

  24. 24

    istio exclut le service de ext-auth

  25. 25

    istio JWT authentication for single service behind ingress gateway

  26. 26

    How to host multiple applications in one Istio service mesh?

  27. 27

    How to use a Google Secret in a deployed Cloud Run Service (managed)?

  28. 28

    Kubernetes ExternalName service not visible in DNS

  29. 29

    Kubernetes MLflow Service Pod Connection

ホットタグ

アーカイブ