Todos os produtos
Search

Este produto

    Alibaba Cloud Service Mesh:Exportar dados de rastreamento do ASM para um sistema autogerenciado

    Central de documentação

    Alibaba Cloud Service Mesh:Exportar dados de rastreamento do ASM para um sistema autogerenciado

    Última atualização: Sep 17, 2026

    Se a versão da sua instância do Service Mesh (ASM) for anterior à v1.18.0.124, você só poderá exportar os dados de rastreamento para um sistema autogerenciado compatível com Zipkin. Se a instância do ASM for v1.18.0.124 ou posterior, a exportação ocorrerá exclusivamente para o Managed Service for OpenTelemetry. Este tópico descreve como exportar dados de rastreamento do ASM para um sistema autogerenciado compatível com Zipkin ou para o Managed Service for OpenTelemetry.

    Pré-requisitos

    • Um sistema autogerenciado compatível com Zipkin está configurado e escutando na porta 9411 do servidor Zipkin. Se você usar Jaeger, implante os coletores do Zipkin.

    • O sistema autogerenciado está implantado em um cluster no plano de dados.

    • Uma instância do ASM foi criada e um cluster Kubernetes foi adicionado a ela. Para mais informações, consulte Add a cluster to an ASM instance.

    • Um gateway de entrada foi criado na instância do ASM. Para mais informações, consulte Create an ingress gateway.

    Procedimento

    Execute as operações conforme a versão da sua instância do ASM.

    Para uma instância do ASM v1.18.0.124 ou posterior

    Etapa 1: Implantar o Zipkin

    1. Execute o comando abaixo para criar um namespace chamado zipkin destinado à implantação do Zipkin:

      kubectl create namespace zipkin

    2. Instale o Zipkin usando o Helm com o seguinte comando:

      helm install --namespace zipkin my-zipkin carlosjgp/zipkin --version 0.2.0

    3. Verifique se o Zipkin está funcionando corretamente com este comando:

      kubectl -n zipkin get pods

      Saída esperada:

      NAME                                   READY   STATUS    RESTARTS   AGE
my-zipkin-collector-79c6dc9cd7-jmswm   1/1     Running   0          29m
my-zipkin-ui-64c97b4d6c-f742j          1/1     Running   0          29m

    Etapa 2: Implantar o OpenTelemetry Operator

    1. No ambiente kubeconfig do seu cluster ACK, execute o comando a seguir para criar o namespace opentelemetry-operator-system:

      kubectl create namespace opentelemetry-operator-system

    2. Instale o OpenTelemetry Operator no namespace opentelemetry-operator-system usando o Helm com o comando abaixo:

      helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts
helm install --namespace=opentelemetry-operator-system opentelemetry-operator open-telemetry/opentelemetry-operator \
  --set "manager.collectorImage.repository=otel/opentelemetry-collector-k8s" \
  --set admissionWebhooks.certManager.enabled=false \
  --set admissionWebhooks.autoGenerateCert.enabled=true

    3. Confirme se o OpenTelemetry Operator está em execução adequada com este comando:

      kubectl get pod -n opentelemetry-operator-system

      Saída esperada:

      NAME                                      READY   STATUS    RESTARTS   AGE
opentelemetry-operator-854fb558b5-pvllj   2/2     Running   0          1m

      Um STATUS definido como Running indica que o OpenTelemetry Operator está ativo.

    Etapa 3: Criar um OpenTelemetry Collector

    1. Crie um arquivo collector.yaml contendo o conteúdo exibido no bloco de código a seguir.

      Substitua ${ENDPOINT} no arquivo YAML por um endpoint de virtual private cloud (VPC) que suporte o protocolo gRPC. Substitua ${TOKEN} pelo token de autenticação. Para obter detalhes sobre como conseguir os endpoints suportados pelo Managed Service for OpenTelemetry e os tokens de autenticação, consulte Connect to Managed Service for OpenTelemetry and authenticate clients.

      Show the collector.yaml file

      apiVersion: opentelemetry.io/v1alpha1
kind: OpenTelemetryCollector
metadata:
  labels:
    app.kubernetes.io/managed-by: opentelemetry-operator
  name: default
  namespace: opentelemetry-operator-system
  annotations:
    sidecar.istio.io/inject: "false"
spec:
  config: |
    extensions:
      memory_ballast:
        size_mib: 512
      zpages:
        endpoint: 0.0.0.0:55679
    receivers:
      otlp:
        protocols:
          grpc:
            endpoint: "0.0.0.0:4317"
    exporters:
      debug:
      zipkin:
      	endpoint: http://my-zipkin-collector.zipkin.svc.cluster.local:9411/api/v2/spans
    service:
      pipelines:
        traces:
          receivers: [otlp]
          processors: []
          exporters: [zipkin, debug]
  ingress:
    route: {}
  managementState: managed
  mode: deployment
  observability:
    metrics: {}
  podDisruptionBudget:
    maxUnavailable: 1
  replicas: 1
  resources: {}
  targetAllocator:
    prometheusCR:
      scrapeInterval: 30s
    resources: {}
  upgradeStrategy: automatic

    2. Conecte-se a um cluster Container Service for Kubernetes (ACK) via kubectl utilizando as informações do arquivo kubeconfig e implante o OpenTelemetry Collector no cluster com o comando:

      kubectl apply -f collector.yaml

    3. Valide se o OpenTelemetry Collector foi iniciado executando o comando abaixo:

      kubectl get pod -n opentelemetry-operator-system

      Saída esperada:

      NAME                                      READY   STATUS    RESTARTS   AGE
opentelemetry-operator-854fb558b5-pvllj   2/2     Running   0          3m
default-collector-5cbb4497f4-2hjqv        1/1     Running   0          30s

      Essa saída confirma que o OpenTelemetry Collector iniciou normalmente.

    4. Verifique se existe um service criado para o OpenTelemetry Collector com este comando:

      kubectl get svc -n opentelemetry-operator-system

      Saída esperada:

      opentelemetry-operator           ClusterIP   172.16.138.165   <none>        8443/TCP,8080/TCP   3m
opentelemetry-operator-webhook   ClusterIP   172.16.127.0     <none>        443/TCP             3m
default-collector              ClusterIP   172.16.145.93    <none>        4317/TCP   30s
default-collector-headless     ClusterIP   None             <none>        4317/TCP   30s
default-collector-monitoring   ClusterIP   172.16.136.5     <none>        8888/TCP   30s

      A saída acima demonstra que um service foi provisionado para o OpenTelemetry Collector.

    Etapa 4: Implantar aplicações de teste

    1. Implante a aplicação de exemplo Bookinfo.

      1. Crie o arquivo bookinfo.yaml com o conteúdo a seguir.

        Expand to viewYAMLYAML content

        apiVersion: v1
kind: Service
metadata:
  name: details
  labels:
    app: details
    service: details
spec:
  ports:
  - port: 9080
    name: http
  selector:
    app: details
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: bookinfo-details
  labels:
    account: details
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: details-v1
  labels:
    app: details
    version: v1
spec:
  replicas: 1
  selector:
    matchLabels:
      app: details
      version: v1
  template:
    metadata:
      labels:
        app: details
        version: v1
    spec:
      serviceAccountName: bookinfo-details
      containers:
      - name: details
        image: registry-cn-hangzhou.ack.aliyuncs.com/ack-demo/examples-bookinfo-details-v1:1.20.1
        imagePullPolicy: IfNotPresent
        ports:
        - containerPort: 9080
---
##################################################################################################
# Ratings service
##################################################################################################
apiVersion: v1
kind: Service
metadata:
  name: ratings
  labels:
    app: ratings
    service: ratings
spec:
  ports:
  - port: 9080
    name: http
  selector:
    app: ratings
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: bookinfo-ratings
  labels:
    account: ratings
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: ratings-v1
  labels:
    app: ratings
    version: v1
spec:
  replicas: 1
  selector:
    matchLabels:
      app: ratings
      version: v1
  template:
    metadata:
      labels:
        app: ratings
        version: v1
    spec:
      serviceAccountName: bookinfo-ratings
      containers:
      - name: ratings
        image: registry-cn-hangzhou.ack.aliyuncs.com/ack-demo/examples-bookinfo-ratings-v1:1.20.1
        imagePullPolicy: IfNotPresent
        ports:
        - containerPort: 9080
---
##################################################################################################
# Reviews service
##################################################################################################
apiVersion: v1
kind: Service
metadata:
  name: reviews
  labels:
    app: reviews
    service: reviews
spec:
  ports:
  - port: 9080
    name: http
  selector:
    app: reviews
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: bookinfo-reviews
  labels:
    account: reviews
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: reviews-v1
  labels:
    app: reviews
    version: v1
spec:
  replicas: 1
  selector:
    matchLabels:
      app: reviews
      version: v1
  template:
    metadata:
      labels:
        app: reviews
        version: v1
    spec:
      serviceAccountName: bookinfo-reviews
      containers:
      - name: reviews
        image: registry-cn-hangzhou.ack.aliyuncs.com/ack-demo/examples-bookinfo-reviews-v1:1.20.1
        imagePullPolicy: IfNotPresent
        env:
        - name: LOG_DIR
          value: "/tmp/logs"
        ports:
        - containerPort: 9080
        volumeMounts:
        - name: tmp
          mountPath: /tmp
        - name: wlp-output
          mountPath: /opt/ibm/wlp/output
      volumes:
      - name: wlp-output
        emptyDir: {}
      - name: tmp
        emptyDir: {}
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: reviews-v2
  labels:
    app: reviews
    version: v2
spec:
  replicas: 1
  selector:
    matchLabels:
      app: reviews
      version: v2
  template:
    metadata:
      labels:
        app: reviews
        version: v2
    spec:
      serviceAccountName: bookinfo-reviews
      containers:
      - name: reviews
        image: registry-cn-hangzhou.ack.aliyuncs.com/ack-demo/examples-bookinfo-reviews-v2:1.20.1
        imagePullPolicy: IfNotPresent
        env:
        - name: LOG_DIR
          value: "/tmp/logs"
        ports:
        - containerPort: 9080
        volumeMounts:
        - name: tmp
          mountPath: /tmp
        - name: wlp-output
          mountPath: /opt/ibm/wlp/output
      volumes:
      - name: wlp-output
        emptyDir: {}
      - name: tmp
        emptyDir: {}
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: reviews-v3
  labels:
    app: reviews
    version: v3
spec:
  replicas: 1
  selector:
    matchLabels:
      app: reviews
      version: v3
  template:
    metadata:
      labels:
        app: reviews
        version: v3
    spec:
      serviceAccountName: bookinfo-reviews
      containers:
      - name: reviews
        image: registry-cn-hangzhou.ack.aliyuncs.com/ack-demo/examples-bookinfo-reviews-v3:1.20.1
        imagePullPolicy: IfNotPresent
        env:
        - name: LOG_DIR
          value: "/tmp/logs"
        ports:
        - containerPort: 9080
        volumeMounts:
        - name: tmp
          mountPath: /tmp
        - name: wlp-output
          mountPath: /opt/ibm/wlp/output
      volumes:
      - name: wlp-output
        emptyDir: {}
      - name: tmp
        emptyDir: {}
---
##################################################################################################
# Productpage services
##################################################################################################
apiVersion: v1
kind: Service
metadata:
  name: productpage
  labels:
    app: productpage
    service: productpage
spec:
  ports:
  - port: 9080
    name: http
  selector:
    app: productpage
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: bookinfo-productpage
  labels:
    account: productpage
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: productpage-v1
  labels:
    app: productpage
    version: v1
spec:
  replicas: 1
  selector:
    matchLabels:
      app: productpage
      version: v1
  template:
    metadata:
      annotations:
        prometheus.io/scrape: "true"
        prometheus.io/port: "9080"
        prometheus.io/path: "/metrics"
      labels:
        app: productpage
        version: v1
    spec:
      serviceAccountName: bookinfo-productpage
      containers:
      - name: productpage
        image: registry-cn-hangzhou.ack.aliyuncs.com/ack-demo/examples-bookinfo-productpage-v1:1.20.1
        imagePullPolicy: IfNotPresent
        ports:
        - containerPort: 9080
        volumeMounts:
        - name: tmp
          mountPath: /tmp
      volumes:
      - name: tmp
        emptyDir: {}
---

      2. Implante a aplicação Bookinfo no cluster do plano de dados.

        kubectl --kubeconfig=${DATA_PLANE_KUBECONFIG} apply -f bookinfo.yaml

    2. Implante a aplicação sleep.

      1. Crie um arquivo chamado sleep.yaml com o conteúdo abaixo.

        Sleep.yaml

        apiVersion: v1
kind: ServiceAccount
metadata:
  name: sleep
---
apiVersion: v1
kind: Service
metadata:
  name: sleep
  labels:
    app: sleep
    service: sleep
spec:
  ports:
  - port: 80
    name: http
  selector:
    app: sleep
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: sleep
spec:
  replicas: 1
  selector:
    matchLabels:
      app: sleep
  template:
    metadata:
      labels:
        app: sleep
    spec:
      terminationGracePeriodSeconds: 0
      serviceAccountName: sleep
      containers:
      - name: sleep
        image: registry.cn-hangzhou.aliyuncs.com/acs/curl:8.1.2
        command: ["/bin/sleep", "infinity"]
        imagePullPolicy: IfNotPresent
        volumeMounts:
        - mountPath: /etc/sleep/tls
          name: secret-volume
      volumes:
      - name: secret-volume
        secret:
          secretName: sleep-secret
          optional: true
---

      2. Implante a aplicação sleep.

        kubectl --kubeconfig=${DATA_PLANE_KUBECONFIG} apply -f sleep.yaml

    Etapa 5: Acessar a aplicação productpage e visualizar os dados de rastreamento

    1. Acesse a aplicação productpage executando o comando a seguir:

      kubectl exec -it deploy/sleep -c sleep -- curl  productpage:9080/productpage?u=normal

    2. Após o acesso bem-sucedido, visualize os logs do OpenTelemetry Collector e a saída impressa pelo debug exporter.

      2023-11-20T08:44:27.531Z	info	TracesExporter	{"kind": "exporter", "data_type": "traces", "name": "debug", "resource spans": 1, "spans": 3}

    Etapa 6: Configurar um gateway do ASM e visualizar dados de rastreamento no serviço Zipkin

    1. Crie um gateway Istio.

      1. Utilize o conteúdo abaixo para criar o arquivo ingressgateway.yaml:

        Expand to view the ingressgateway.yaml file

        apiVersion: networking.istio.io/v1beta1
kind: Gateway
metadata:
  name: ingressgateway
  namespace: istio-system
spec:
  selector:
    istio: ingressgateway
  servers:
    - hosts:
        - '*'
      port:
        name: http
        number: 80
        protocol: HTTP
---
apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
  name: ingressgateway
  namespace: istio-system
spec:
  gateways:
    - ingressgateway
  hosts:
    - '*'
  http:
    - route:
        - destination:
            host: my-zipkin-collector.zipkin.svc.cluster.local
            port:
              number: 9411

      2. Conecte-se à instância do ASM via kubectl usando as informações do arquivo kubeconfig. Em seguida, configure o gateway do ASM para escutar na porta 80 e defina uma rota para o serviço Zipkin com o comando:

        kubectl apply -f ingressgateway.yaml

    2. Acesse o serviço Zipkin utilizando o endereço IP do gateway do ASM para visualizar os dados de rastreamento.

      image.png

    Para uma instância do ASM com versão anterior à v1.18.0.124

    Etapa 1: Ativar o recurso de rastreamento na instância do ASM

    • Para instâncias do ASM com versão anterior à v1.17.2.28, ative o rastreamento seguindo estes passos: faça login no console do ASM. Na página Base Information da instância, clique em Settings. Na tela seguinte, selecione Enable Tracing Analysis, ajuste os parâmetros necessários e clique em OK.

    • Caso a versão da instância seja v1.17.2.28 ou superior, habilite o rastreamento consultando a seção "Description of Tracing Analysis Settings" em Configure Observability Settings.

    Etapa 2: Implantar o Zipkin no cluster Kubernetes do plano de dados

    1. Crie um arquivo zipkin-server.yaml utilizando o conteúdo a seguir:

      Expand to view the zipkin-server.yaml file

      apiVersion: apps/v1
kind: Deployment
metadata:
  name: zipkin-server
  namespace: istio-system
spec:
  replicas: 1
  selector:
    matchLabels:
      app: zipkin-server
      component: zipkin
  template:
   metadata:
    labels:
      app: zipkin-server
      component: zipkin
   spec:
    containers:
     - name: zipkin-server
       image: openzipkin/zipkin
       imagePullPolicy: IfNotPresent
       readinessProbe:
            httpGet:
              path: /health
              port: 9411
            initialDelaySeconds: 5
            periodSeconds: 5
      Nota

      Ao utilizar um arquivo YAML personalizado para implantar o Zipkin, certifique-se de que a implantação ocorra no namespace istio-system.

    2. Implante o Zipkin no cluster Kubernetes do plano de dados executando o comando abaixo:

      kubectl --kubeconfig=${DATA_PLANE_KUBECONFIG} apply -f zipkin-server.yaml
      Nota

      Se estiver usando o código de exemplo deste tópico, substitua ${DATA_PLANE_KUBECONFIG} no comando pelo caminho do arquivo kubeconfig do cluster Kubernetes no plano de dados. Além disso, substitua ${ASM_KUBECONFIG} pelo caminho do arquivo kubeconfig da instância do ASM.

    3. Após concluir a implantação anterior, verifique se o pod onde o servidor Zipkin reside iniciou corretamente.

    Etapa 3: Criar um service para expor o servidor Zipkin

    Crie um service denominado zipkin no namespace istio-system para receber os dados de rastreamento do ASM.

    • Para expor o servidor Zipkin à internet, utilize o arquivo zipkin-svc-expose-public.yaml.

    • Caso contrário, use o arquivo zipkin-svc.yaml.

    Neste exemplo, utilizamos o arquivo zipkin-svc-expose-public.yaml para expor o servidor Zipkin publicamente, facilitando a visualização dos dados de rastreamento.

    Nota

    O nome do service criado deve ser obrigatoriamente zipkin.

    1. Crie um arquivo YAML conforme suas necessidades de negócio usando o código abaixo.

      • Para expor o servidor Zipkin à internet, utilize o arquivo zipkin-svc-expose-public.yaml com o seguinte conteúdo:

        Expand to view the zipkin-svc-expose-public.yaml file

        apiVersion: v1
kind: Service
metadata:
  labels:
    app: tracing
    component: zipkin
  name: zipkin
  namespace: istio-system
spec:
  ports:
  - name: zipkin
    port: 9411
    protocol: TCP
    targetPort: 9411
  selector:
    app: zipkin-server
    component: zipkin
  type: LoadBalancer

      • Se não for necessário expor o servidor Zipkin à internet, utilize o arquivo zipkin-svc.yaml com o conteúdo abaixo:

        Expand to view the zipkin-svc.yaml file

        apiVersion: v1
kind: Service
metadata:
  labels:
    app: tracing
    component: zipkin
  name: zipkin
  namespace: istio-system
spec:
  ports:
  - name: zipkin
    port: 9411
    protocol: TCP
    targetPort: 9411
  selector:
    app: zipkin-server
    component: zipkin
  type: ClusterIP
      Nota

      Ao usar um arquivo YAML personalizado para implantar o service zipkin, garanta que ele esteja no namespace istio-system.

    2. Execute os comandos a seguir para implantar o service zipkin no cluster Kubernetes do plano de dados:

      # Deploy the zipkin service to expose the Zipkin server to the internal network. 
kubectl --kubeconfig=${DATA_PLANE_KUBECONFIG} apply -f zipkin-svc.yaml
# Deploy the zipkin service to expose the Zipkin server to the Internet. 
kubectl --kubeconfig=${DATA_PLANE_KUBECONFIG} apply -f zipkin-svc-expose-public.yaml

    Etapa 4: Implantar a aplicação Bookinfo

    1. Implante a aplicação Bookinfo no cluster Kubernetes do plano de dados com o comando:

      kubectl --kubeconfig=${DATA_PLANE_KUBECONFIG} apply -f bookinfo.yaml

      Expand to view the bookinfo.yaml file

      apiVersion: v1
kind: Service
metadata:
  name: details
  labels:
    app: details
    service: details
spec:
  ports:
  - port: 9080
    name: http
  selector:
    app: details
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: bookinfo-details
  labels:
    account: details
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: details-v1
  labels:
    app: details
    version: v1
spec:
  replicas: 1
  selector:
    matchLabels:
      app: details
      version: v1
  template:
    metadata:
      labels:
        app: details
        version: v1
    spec:
      serviceAccountName: bookinfo-details
      containers:
      - name: details
        image: docker.io/istio/examples-bookinfo-details-v1:1.16.2
        imagePullPolicy: IfNotPresent
        ports:
        - containerPort: 9080
---
##################################################################################################
# Ratings service
##################################################################################################
apiVersion: v1
kind: Service
metadata:
  name: ratings
  labels:
    app: ratings
    service: ratings
spec:
  ports:
  - port: 9080
    name: http
  selector:
    app: ratings
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: bookinfo-ratings
  labels:
    account: ratings
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: ratings-v1
  labels:
    app: ratings
    version: v1
spec:
  replicas: 1
  selector:
    matchLabels:
      app: ratings
      version: v1
  template:
    metadata:
      labels:
        app: ratings
        version: v1
    spec:
      serviceAccountName: bookinfo-ratings
      containers:
      - name: ratings
        image: docker.io/istio/examples-bookinfo-ratings-v1:1.16.2
        imagePullPolicy: IfNotPresent
        ports:
        - containerPort: 9080
---
##################################################################################################
# Reviews service
##################################################################################################
apiVersion: v1
kind: Service
metadata:
  name: reviews
  labels:
    app: reviews
    service: reviews
spec:
  ports:
  - port: 9080
    name: http
  selector:
    app: reviews
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: bookinfo-reviews
  labels:
    account: reviews
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: reviews-v1
  labels:
    app: reviews
    version: v1
spec:
  replicas: 1
  selector:
    matchLabels:
      app: reviews
      version: v1
  template:
    metadata:
      labels:
        app: reviews
        version: v1
    spec:
      serviceAccountName: bookinfo-reviews
      containers:
      - name: reviews
        image: docker.io/istio/examples-bookinfo-reviews-v1:1.16.2
        imagePullPolicy: IfNotPresent
        env:
        - name: LOG_DIR
          value: "/tmp/logs"
        ports:
        - containerPort: 9080
        volumeMounts:
        - name: tmp
          mountPath: /tmp
        - name: wlp-output
          mountPath: /opt/ibm/wlp/output
      volumes:
      - name: wlp-output
        emptyDir: {}
      - name: tmp
        emptyDir: {}
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: reviews-v2
  labels:
    app: reviews
    version: v2
spec:
  replicas: 1
  selector:
    matchLabels:
      app: reviews
      version: v2
  template:
    metadata:
      labels:
        app: reviews
        version: v2
    spec:
      serviceAccountName: bookinfo-reviews
      containers:
      - name: reviews
        image: docker.io/istio/examples-bookinfo-reviews-v2:1.16.2
        imagePullPolicy: IfNotPresent
        env:
        - name: LOG_DIR
          value: "/tmp/logs"
        ports:
        - containerPort: 9080
        volumeMounts:
        - name: tmp
          mountPath: /tmp
        - name: wlp-output
          mountPath: /opt/ibm/wlp/output
      volumes:
      - name: wlp-output
        emptyDir: {}
      - name: tmp
        emptyDir: {}
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: reviews-v3
  labels:
    app: reviews
    version: v3
spec:
  replicas: 1
  selector:
    matchLabels:
      app: reviews
      version: v3
  template:
    metadata:
      labels:
        app: reviews
        version: v3
    spec:
      serviceAccountName: bookinfo-reviews
      containers:
      - name: reviews
        image: docker.io/istio/examples-bookinfo-reviews-v3:1.16.2
        imagePullPolicy: IfNotPresent
        env:
        - name: LOG_DIR
          value: "/tmp/logs"
        ports:
        - containerPort: 9080
        volumeMounts:
        - name: tmp
          mountPath: /tmp
        - name: wlp-output
          mountPath: /opt/ibm/wlp/output
      volumes:
      - name: wlp-output
        emptyDir: {}
      - name: tmp
        emptyDir: {}
---
##################################################################################################
# Productpage services
##################################################################################################
apiVersion: v1
kind: Service
metadata:
  name: productpage
  labels:
    app: productpage
    service: productpage
spec:
  ports:
  - port: 9080
    name: http
  selector:
    app: productpage
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: bookinfo-productpage
  labels:
    account: productpage
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: productpage-v1
  labels:
    app: productpage
    version: v1
spec:
  replicas: 1
  selector:
    matchLabels:
      app: productpage
      version: v1
  template:
    metadata:
      labels:
        app: productpage
        version: v1
    spec:
      serviceAccountName: bookinfo-productpage
      containers:
      - name: productpage
        image: docker.io/istio/examples-bookinfo-productpage-v1:1.16.2
        imagePullPolicy: IfNotPresent
        ports:
        - containerPort: 9080
        volumeMounts:
        - name: tmp
          mountPath: /tmp
      volumes:
      - name: tmp
        emptyDir: {}
---

    2. No cliente kubectl, implante os virtual services para o Bookinfo executando:

      kubectl --kubeconfig=${ASM_KUBECONFIG} apply -f virtual-service-all-v1.yaml

      Expand to view the virtual-service-all-v1.yaml file

      apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: productpage
spec:
  hosts:
  - productpage
  http:
  - route:
    - destination:
        host: productpage
        subset: v1
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: reviews
spec:
  hosts:
  - reviews
  http:
  - route:
    - destination:
        host: reviews
        subset: v1
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: ratings
spec:
  hosts:
  - ratings
  http:
  - route:
    - destination:
        host: ratings
        subset: v1
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: details
spec:
  hosts:
  - details
  http:
  - route:
    - destination:
        host: details
        subset: v1
---

    3. Configure as destination rules para o Bookinfo no cliente kubectl com o comando:

      kubectl --kubeconfig=${ASM_KUBECONFIG} apply -f destination-rule-all.yaml

      Expand to view the destination-rule-all.yaml file

      apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: productpage
spec:
  host: productpage
  subsets:
  - name: v1
    labels:
      version: v1
---
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: reviews
spec:
  host: reviews
  subsets:
  - name: v1
    labels:
      version: v1
  - name: v2
    labels:
      version: v2
  - name: v3
    labels:
      version: v3
---
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: ratings
spec:
  host: ratings
  subsets:
  - name: v1
    labels:
      version: v1
  - name: v2
    labels:
      version: v2
  - name: v2-mysql
    labels:
      version: v2-mysql
  - name: v2-mysql-vm
    labels:
      version: v2-mysql-vm
---
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: details
spec:
  host: details
  subsets:
  - name: v1
    labels:
      version: v1
  - name: v2
    labels:
      version: v2
---

    4. Implante um gateway para o Bookinfo através do cliente kubectl executando:

      kubectl --kubeconfig=${ASM_KUBECONFIG} apply -f bookinfo-gateway.yaml

      Expand to view the bookinfo-gateway.yaml file

      apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: bookinfo-gateway
spec:
  selector:
    istio: ingressgateway # use istio default controller
  servers:
  - port:
      number: 80
      name: http
      protocol: HTTP
    hosts:
    - "*"
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: bookinfo
spec:
  hosts:
  - "*"
  gateways:
  - bookinfo-gateway
  http:
  - match:
    - uri:
        exact: /productpage
    - uri:
        prefix: /static
    - uri:
        exact: /login
    - uri:
        exact: /logout
    - uri:
        prefix: /api/v1/products
    route:
    - destination:
        host: productpage
        port:
          number: 9080

    Etapa 5: Gerar dados de rastreamento

    1. Obtenha o endereço IP do gateway de entrada com o comando:

      kubectl --kubeconfig=${DATA_PLANE_KUBECONFIG} get svc -n istio-system|grep ingressgateway|awk -F ' ' '{print $4}'

    2. Insira IP address of the ingress gateway/productpage na barra de endereços do navegador para acessar o Bookinfo.

    Etapa 6: Visualizar dados de rastreamento

    1. Recupere o endereço do service zipkin executando:

      kubectl --kubeconfig=${DATA_PLANE_KUBECONFIG}get svc -n istio-system|grep zipkin|awk -F ' ' '{print $4}'

    2. Digite IP address of the zipkin service:9411 na barra de endereços do seu navegador para abrir o console do Zipkin e visualizar os dados de rastreamento.

      链路追踪