k8s之炉火纯青之pinpoint链路追踪

已于 2022-07-05 17:32:47 修改
阅读量1.3k 收藏
点赞数 1
分类专栏： pinpoint 文章标签： 云
于 2022-07-04 11:32:12 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/HYMajor/article/details/125596787
版权

k8s搭建pinpoint–zookeeper

1、创建目录和专用的名称空间

mkdir -p /data/yaml/pinpoint && cd /data/yaml/pinpoint
kubectl create ns pinpoint

2、部署zookeepers

mkdir -p /data/yaml/pinpoint/zookeepers && cd /data/yaml/pinpoint/zookeepers


vim zoo1.yaml
apiVersion: v1
kind: Service
metadata:
    namespace: pinpoint
    labels:
      app: zoo1
    name: zoo1
spec:
   ports:
   - name: httpa
     targetPort: 2181
     port: 2181
   - name: httpb
     targetPort: 2888
     port: 2888
   - name: httpc
     targetPort: 3888
     port: 3888
   selector:
     app: zoo1
---
kind: Deployment
apiVersion: apps/v1
metadata:
  namespace: pinpoint
  name: zoo1
  labels:
     app: zoo1
spec:
  replicas: 1
  minReadySeconds: 120
  strategy:
    type: RollingUpdate
    rollingUpdate:
       maxSurge: 1
       maxUnavailable: 0
  selector:
    matchLabels:
      app: zoo1
  template:
    metadata:
       labels:
          app: zoo1
    spec:
       terminationGracePeriodSeconds: 60
       hostname: zoo1
       containers:
       - name: zoo1
         image: harbor.junengcloud.com/pinpoint/zookeeper:3.4
         imagePullPolicy: IfNotPresent
         resources:
           requests:
             cpu: 100m
             memory: 204Mi
           limits:
             cpu: 2000m
             memory: 2048Mi
         ports:
         - containerPort: 2181
           name: httpa
         - containerPort: 2888
           name: httpb
         - containerPort: 3888
           name: httpc
         livenessProbe:
           tcpSocket:
              port: 2181
           initialDelaySeconds: 60
           periodSeconds: 180
         env:
         - name: ZOO_MY_ID
           value: "1"
         - name: ZOO_SERVERS
           value: "server.1=0.0.0.0:2888:3888 server.2=zoo2:2888:3888 server.3=zoo3:2888:3888"                              

[root@master zookeepers]# vim zoo2.yaml 
apiVersion: v1
kind: Service
metadata:
    namespace: pinpoint
    labels:
      app: zoo2
    name: zoo2
spec:
   ports:
   - name: httpa
     targetPort: 2181
     port: 2181
   - name: httpb
     targetPort: 2888
     port: 2888
   - name: httpc
     targetPort: 3888
     port: 3888
   selector:
     app: zoo2
---
kind: Deployment
apiVersion: apps/v1
metadata:
  namespace: pinpoint
  name: zoo2
  labels:
     app: zoo2
spec:
  replicas: 1
  minReadySeconds: 120
  strategy:
    type: RollingUpdate
    rollingUpdate:
       maxSurge: 1
       maxUnavailable: 0
  selector:
    matchLabels:
      app: zoo2
  template:
    metadata:
       labels:
          app: zoo2
    spec:
       terminationGracePeriodSeconds: 60
       hostname: zoo2
       containers:
       - name: zoo2
         image: harbor.junengcloud.com/pinpoint/zookeeper:3.4
         imagePullPolicy: IfNotPresent
         resources:
           requests:
             cpu: 100m
             memory: 204Mi
           limits:
             cpu: 2000m
             memory: 2048Mi
         ports:
         - containerPort: 2181
           name: httpa
         - containerPort: 2888
           name: httpb
         - containerPort: 3888
           name: httpc
         livenessProbe:
           tcpSocket:
              port: 2181
           initialDelaySeconds: 60
           periodSeconds: 180
         env:
         - name: ZOO_MY_ID
           value: "2"
         - name: ZOO_SERVERS
           value: "server.1=zoo1:2888:3888 server.2=0.0.0.0:2888:3888 server.3=zoo3:2888:3888"

vim zoo3.yaml
apiVersion: v1
kind: Service
metadata:
    namespace: pinpoint
    labels:
      app: zoo3
    name: zoo3
spec:
   ports:
   - name: httpa
     targetPort: 2181
     port: 2181
   - name: httpb
     targetPort: 2888
     port: 2888
   - name: httpc
     targetPort: 3888
     port: 3888
   selector:
     app: zoo3
---
kind: Deployment
apiVersion: apps/v1
metadata:
  namespace: pinpoint
  name: zoo3
  labels:
     app: zoo3
spec:
  replicas: 1
  minReadySeconds: 120
  strategy:
    type: RollingUpdate
    rollingUpdate:
       maxSurge: 1
       maxUnavailable: 0
  selector:
    matchLabels:
      app: zoo3
  template:
    metadata:
       labels:
         app: zoo3
    spec:
       terminationGracePeriodSeconds: 60
       hostname: zoo3
       containers:
       - name: zoo3
         image: harbor.junengcloud.com/pinpoint/zookeeper:3.4
         imagePullPolicy: IfNotPresent
         resources:
           requests:
             cpu: 100m
             memory: 204Mi
           limits:
             cpu: 2000m
             memory: 2048Mi
         ports:
         - containerPort: 2181
           name: httpa
         - containerPort: 2888
           name: httpb
         - containerPort: 3888
           name: httpc
         livenessProbe:
           tcpSocket:
              port: 2181
           initialDelaySeconds: 60
           periodSeconds: 180
         env:
         - name: ZOO_MY_ID
           value: "3"
         - name: ZOO_SERVERS
           value: "server.1=zoo1:2888:3888 server.2=zoo2:2888:3888 server.3=0.0.0.0:2888:3888"

kubectl apply -f  zoo1.yaml
kubectl apply -f  zoo2.yaml
kubectl apply -f  zoo3.yaml

[root@master zookeepers]# kubectl get pods -n pinpoint
NAME                    READY   STATUS    RESTARTS   AGE
zoo1-749d8cc498-bbx4g   1/1     Running   0          3h33m
zoo2-695c9f8755-swnqb   1/1     Running   0          3h28m
zoo3-6bb94d5568-45tft   1/1     Running   0          3h28m

[root@master zookeepers]# kubectl get svc -n pinpoint
NAME   TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                      AGE
zoo1   ClusterIP   10.102.68.14     <none>        2181/TCP,2888/TCP,3888/TCP   178m
zoo2   ClusterIP   10.108.226.102   <none>        2181/TCP,2888/TCP,3888/TCP   3h29m
zoo3   ClusterIP   10.101.11.240    <none>        2181/TCP,2888/TCP,3888/TCP   3h29m
[root@master zookeepers]# 

[root@master zookeepers]# kubectl -n pinpoint exec -it zoo1-749d8cc498-bbx4g   -- zkServer.sh status
ZooKeeper JMX enabled by default
Using config: /conf/zoo.cfg
Mode: follower
You have new mail in /var/spool/mail/root
[root@master zookeepers]# 


[root@master zookeepers]# kubectl -n pinpoint exec -it zoo2-695c9f8755-swnqb    -- zkServer.sh status
ZooKeeper JMX enabled by default
Using config: /conf/zoo.cfg
Mode: follower


[root@master zookeepers]# kubectl -n pinpoint exec -it zoo3-6bb94d5568-45tft   -- zkServer.sh status
ZooKeeper JMX enabled by default
Using config: /conf/zoo.cfg
Mode: leader
You have new mail in /var/spool/mail/root

k8s搭建jobmanager.taskmanager

配置Jobmanager

[root@master zookeepers]# mkdir -p /data/yaml/pinpoint/jobmanager
[root@master zookeepers]# cd /data/yaml/pinpoint/jobmanager/

[root@master jobmanager]# vim deployment.yaml 
kind: Deployment
apiVersion: apps/v1
metadata:
    namespace: pinpoint
    name: jobmanager
    labels:
       app: jobmanager
spec:
   replicas: 1
   minReadySeconds: 60
   strategy:
     type: RollingUpdate
     rollingUpdate:
       maxSurge: 1
       maxUnavailable: 0
   selector:
      matchLabels:
        app: jobmanager
   template:
     metadata:
        labels:
           app: jobmanager
     spec:
        imagePullSecrets:
        - name: harbor
        terminationGracePeriodSeconds: 60
        hostname: jobmanager
        containers:
        - name: jobmanager
          image: harbor.junengcloud.com/pinpoint/flink:1.3.1
          args:
          - jobmanager
          resources:
            requests:
                cpu: 100m
                memory: 204Mi
            limits:
                cpu: 2000m
                memory: 2048Mi
          env:
          - name: JOB_MANAGER_RPC_ADDRESS
            value: jobmanager
          ports:
          - containerPort: 8081
            name: httpa
          - containerPort: 6123
            name: httpb
          livenessProbe:
            tcpSocket:
               port: 8081
            initialDelaySeconds: 60
            periodSeconds: 180

[root@master jobmanager]# vim svc.yaml 
kind: Service
apiVersion: v1
metadata:
      namespace: pinpoint
      name: jobmanager
      labels:
         app: jobmanager
spec:
   ports:
   - name: httpa
     port: 8081
     targetPort: 8081
   - name: httpb
     port: 6123
     targetPort: 6123
   selector:
     app: jobmanager

配置taskMansger

[root@master jobmanager]# mkdir -p /data/yaml/pinpoint/taskmanager
[root@master jobmanager]# cd /data/yaml/pinpoint/taskmanager/

[root@master taskmanager]# vim deployment.yaml 

apiVersion: apps/v1
kind: Deployment
metadata:
      namespace: pinpoint
      name: taskmanager
      labels:
         app: taskmanager
spec:
     replicas: 1
     minReadySeconds: 120
     strategy:
        type: RollingUpdate
        rollingUpdate:
           maxSurge: 1
           maxUnavailable: 0
     selector:
         matchLabels:
             app: taskmanager
     template:
         metadata:
           labels:
              app: taskmanager
         spec:
           imagePullSecrets:
           - name: harbor
           terminationGracePeriodSeconds: 60
           hostname: taskmanager
           containers:
           - name: taskmanager
             image: harbor.junengcloud.com/pinpoint/flink:1.3.1
             args:
             - taskmanager
             resources:
               requests:
                  cpu: 100m
                  memory: 204Mi
               limits:
                  cpu: 2000m
                  memory: 2048Mi
             env:
             - name: JOB_MANAGER_RPC_ADDRESS
               value: jobmanager
             ports:
             - containerPort: 6121
               name: httpa
             - containerPort: 6122
               name: httpb:
             - containerPort: 19994
               name: httpc

[root@master taskmanager]# vim svc.yaml 

kind: Service
apiVersion: v1
metadata:
    namespace: pinpoint
    labels:
        app: taskmanager
    name: taskmanager
spec:
   ports:
   - name: httpa
     port: 6121
     targetPort: 6121
   - name: httpb
     port: 6122
     targetPort: 6122
   - name: httpc
     port: 19994
     targetPort: 19994
   selector:
     app: taskmanager

[root@master taskmanager]# kubectl apply -f deployment.yaml 
deployment.apps/taskmanager created
[root@master taskmanager]# kubectl apply -f svc.yaml 
service/taskmanager created

配置Hbase

[root@master taskmanager]# mkdir -p /data/yaml/pinpoint/pinpoint-hbase
[root@master taskmanager]# cd /data/yaml/pinpoint/pinpoint-hbase/

master:
yum install nfs-utils -y
mkdir /data/volumes -pv
vim /etc/exports
/data/volumes 192.168.10.0/24(rw,no_root_squash)

exportfs -arv
service nfs start
systemctl enable nfs
systemctl status nfs

vim nfs.yaml
apiVersion: v1
kind: Pod
metadata:
  name: test-nfs-volume
spec:
  containers:
  - name: test-nfs
    image: nginx:latest
    imagePullPolicy: IfNotPresent
    ports:
    - containerPort: 80
       protocol: TCP
    volumeMounts:
    - name: nfs-volumes
      mountPath: /usr/share/nginx/html
  volumes:
  - name: nfs-volumes
    nfs:
       path: /data/volumes
       server: 192.168.10.140

kubectl apply -f nfs.yaml

node1/node2
docker load -i nfs-subdir-external-provisioner.tar.gz

master:
vim sericeaccount.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  name: nfs-provisioner
  
  
kubectl create clusterrolebinding nfs-provisioner --clusterrole=cluster-admin --serviceaccount=default:nfs-provisioner


安装nfs-provisioner
mkdir /data/nfs_pro -p
mkdir /data/volume_test/v1

vim /etc/exports
/data/volumes 192.168.10.0/24(rw,no_root_squash)
/data/nfs_pro 192.168.10.0/24(rw,no_root_squash)
/data/volume_test/v1 192.168.10.0/24(rw,no_root_squash)             

exportfs -arv
systemctl restart nfs


vim nfs-deployment.yaml
kind: Deployment
apiVersion: apps/v1
metadata:
   name: nfs-provisioner
spec:
   selector:
      matchLabels:
            app: nfs-provisioner
   replicas: 1
   strategy:
      type: Recreate
   template:
      metadata:
         labels:
            app: nfs-provisioner
      spec:
         serviceAccount: nfs-provisioner
         containers:
         - name: nfs-provisioner
           image: registry.cn-beijing.aliyuncs.com/mydlq/nfs-subdir-external-provisioner:v4.0.0
           imagePullPolicy: IfNotPresent
           volumeMounts:
           - name: nfs-client-root
             mountPath: /persistentvolumes
           env:
           - name: PROVISIONER_NAME
             value: example.com/nfs
           - name: NFS_SERVER
             value: 192.168.10.140
           - name: NFS_PATH
             value: /data/nfs_pro
         volumes:
         - name: nfs-client-root
           nfs:
             server: 192.168.10.140
             path: /data/nfs_pro
             
kubectl apply -f nfs-deployment.yaml

创建storageclass 提供PV
vim nfs-storageclass.yaml

kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
   name: local-storage
provisioner: example.com/nfs


创建pvc,通过storageclass动态生成pv
vim  claim.yaml
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
    name: test-claim1
spec:
   accessModes: ["ReadWriteMany"]
   resources:
      requests:
          storage: 1Gi
   storageClassName: local-storage


node1/node2
yum install nfs-utils -y
service nfs start
systemctl enable nfs

node1:
mkdir /data1
mount -t nfs 192.168.10.140:/data/volumes /data1

node2:
mkdir /data2
mount -t nfs 192.168.10.140:/data/volumes /data2

[root@master pinpoint-hbase]# vim pvc.yaml 

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
   namespace: pinpoint
   name: pinpoint-zookeeper
spec:
   accessModes:
   - ReadWriteOnce
   resources:
     requests:
        storage: 10Gi
   storageClassName:  local-storage
---
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
    namespace: pinpoint
    name: pinpoint-hbase
spec:
    accessModes:
    - ReadWriteOnce
    resources:
       requests:
          storage: 10Gi
    storageClassName: local-storage

[root@master pinpoint-hbase]# vim pv.yaml 

kind: PersistentVolume
apiVersion: v1
metadata:
  namespace: pinpoint
  name: pinpoint-hbase
spec:
  capacity:
     storage: 10Gi
  volumeMode: Filesystem
  accessModes:
  - ReadWriteOnce
  persistentVolumeReclaimPolicy: Delete
  storageClassName: local-storage
  local:
    path: /data/yaml/pinpoint/pinpoint-hbase
  nodeAffinity:
    required:
       nodeSelectorTerms:
       - matchExpressions:
         - key: kubernetes.io/hostname
           operator: In
           values:
           - worker1(hostname)
---
kind: PersistentVolume
apiVersion: v1
metadata:
   namespace: pinpoint
   name: pinpoint-zookeeper
spec:
   capacity:
      storage: 10Gi
   volumeMode: Filesystem
   accessModes:
   - ReadWriteOnce

[root@master pinpoint-hbase]# vim sts.yaml 

kind: StatefulSet
apiVersion: apps/v1
metadata:
   name: pinpoint-hbase
   namespace: pinpoint
spec:
   selector:
     matchLabels:
          app: pinpoint-hbase
   serviceName: pinpoint-hbase
   replicas: 1
   updateStrategy:
      type: RollingUpdate
   template:
     metadata:
       labels:
          app: pinpoint-hbase
     spec:
       nodeName: worker1
       terminationGracePeriodSeconds: 60
       containers:
       - name: pinpoint-hbase
         imagePullPolicy: IfNotPresent
         image: docker.io/pinpointdocker/pinpoint-hbase:latest
         resources:
            requests:
               cpu: 100m
               memory: 2048Mi
            limits:
               cpu: 2000m
               memory: 7Gi
         ports:
         - containerPort: 60000
           protocol: TCP
           name: httpa
         - containerPort: 16010
           protocol: TCP
           name: httpb
         - containerPort: 60020
           protocol: TCP
           name: httpc
         - containerPort: 16030
           protocol: TCP
           name: httpd
         livenessProbe:
           tcpSocket:
             port: 60000
           initialDelaySeconds: 180
           periodSeconds: 120
         volumeMounts:
         - mountPath: /etc/localtime
           readOnly: false
           name: time-data
         - mountPath: /home/pinpoint/hbase
           name: hbase
         - mountPath: /home/pinpoint/zookeeper
           name: zookeeper
       volumes:
       - name: time-data
         hostPath:
          path: /usr/share/zoneinfo/Asia/Shanghai
       - name: hbase
         persistentVolumeClaim:
            claimName: pinpoint-hbase
       - name: zookeeper
         persistentVolumeClaim:
             claimName: pinpoint-zookeeper

[root@master pinpoint-hbase]# vim svc.yaml 

kind: Service
apiVersion: v1
metadata:
  namespace: pinpoint
  labels:
     app: pinpoint-hbase
  name: pinpoint-hbase
spec:
  ports:
  - name: httpa
    port: 60000
    targetPort: 60000
  - name: httpb
    port: 16010
    targetPort: 16010
  - name: httpc
    port: 60020
    targetPort: 60020
  - name: httpd
    port: 16030
    targetPort: 16030
  selector:
    app: pinpoint-hbase

配置pinpoint-collector

[root@master ~]# mkdir -p /data/yaml/pinpoint/pinpoint-collector
[root@master ~]# cd /data/yaml/pinpoint/pinpoint-collector/
[root@master pinpoint-collector]# vim deployment.yaml

[root@master pinpoint-collector]# vim deployment.yaml 

kind: Deployment
apiVersion: apps/v1
metadata:
   namespace: pinpoint
   name: pinpoint-collector
   labels:
     app: pinpoint-collector
spec:
   replicas: 1
   minReadySeconds: 120
   strategy:
       type: RollingUpdate
       rollingUpdate:
          maxSurge: 1
          maxUnavailable: 0
   selector:
     matchLabels:
       app: pinpoint-collector
   template:
     metadata:
       labels:
          app: pinpoint-collector
     spec:
       imagePullSecrets:
       - name: harbor
       terminationGracePeriodSeconds: 60
       hostname: pinpoint-collector
       containers:
       - name:  pinpoint-collector
         image: harbor.junengcloud.com/pinpoint/pinpoint-collector:2.1.0
         resources:
           requests:
             cpu: 200m
             memory: 307Mi
           limits:
             cpu: 3000m
             memory: 4Gi
         ports:
         - containerPort: 9994
           name: httpa
         - containerPort: 9992
           name: httpb
         - containerPort: 9993
           name: httpc
         - containerPort: 9995
           name: httpd
         - containerPort: 9996
           name: httpe
         - containerPort: 9997
           name: httpf
         - containerPort: 9998
           protocol: UDP
           name: httpg
         - containerPort: 9999
           protocol: UDP
           name: httph
         livenessProbe:
           tcpSocket:
               port: 9991
           initialDelaySeconds: 60
           periodSeconds: 180
         env:
         - name: CLUSTER_ENABLE
           value: "true"
         - name: FLINK_CLUSTER_ENABLE
           value: "true"
         - name: FLINK_CLUSTER_ZOOKEEPER_ADDRESS
           value: "zoo1"
         - name: PINPOINT_ZOOKEEPER_ADDRESS
           value: "zoo1"
         - name: SPRING_PROFILES_ACTIVE
           value: "release"
         - name: HBASE_CLIENT_HOST
         - name: HBASE_CLIENT_HOST
           value: "zoo1"
         - name: HBASE_HOST
           value: "zoo1"
         - name: HBASE_PORT
           value: "2181"
         - name: COLLECTOR_RECEIVER_GRPC_SPAN_WORKER_EXECUTOR_THREAD_SIZE
           value: "256"

vim svc.yaml

apiVersion: v1
kind: Service
metadata:
  namespace: pinpoint
  labels:
    app: pinpoint-collector
  name: pinpoint-collector
spec:
  ports:
  - name: httpa
    port: 9991
    targetPort: 9991
    nodePort: 30091
  - name: httpb
    port: 9992
    targetPort: 9992
    nodePort: 30092
  - name: httpc
    port: 9993
    targetPort: 9993
    nodePort: 30093
  - name: httpd
    port: 9994
    targetPort: 9994
    nodePort: 30094
  - name: httpe
    port: 9995
    targetPort: 9995
    nodePort: 30095
  - name: httpf
    port: 9996
    targetPort: 9996
    nodePort: 30096
  - name: httpg
    port: 9995
    protocol: UDP
    targetPort: 30095
  - name: httph
    port: 9996
    protocol: UDP
    targetPort: 30096
  selector:
    app: pinpoint-collector
  type: NodePort
  
  
kubectl apply -f deployment.yaml
kubectl apply -f svc.yaml

配置pinpoint-web

mkdir -p /data/yaml/pinpoint/pinpoint-web
cd /data/yaml/pinpoint/pinpoint-web
docker pull pinpointdocker/pinpoint-web

vim deployment.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  namespace: pinpoint
  name: pinpoint-web
  labels:
    app: pinpoint-web
spec:
  replicas: 1
  minReadySeconds: 120
  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxSurge: 1
      maxUnavailable: 0
  selector:
    matchLabels:
      app: pinpoint-web
  template:
    metadata:
      labels:
        app: pinpoint-web
    spec:
      terminationGracePeriodSeconds: 60
      hostname: pinpoint-web
      containers:
      - name: pinpoint-web
        image: docker.io/pinpointdocker/pinpoint-web:latest
        resources:
          requests:
            cpu: 100m
            memory: 204Mi
          limits:
            cpu: 2000m
            memory: 2048Mi
        env:
        - name: ADMIN_PASSWORD
          value: "admin"
        - name: ALARM_MAIL_DEBUG
          value: "false"
        - name: ALARM_MAIL_SENDER_ADDRESS
          value: "762359676@qq.com"
        - name: ALARM_MAIL_SERVER_PASSWORD
          value: "mjh123"
        - name: ALARM_MAIL_SERVER_PORT
          value: "465"
        - name: ALARM_MAIL_SERVER_URL
          value: "192.168.10.140"
        - name: ALARM_MAIL_SERVER_USERNAME
          value: "system"
        - name: ALARM_MAIL_SMTP_AUTH
          value: "false"
        - name: ALARM_MAIL_SMTP_PORT
          value: "25"
        - name: ALARM_MAIL_SMTP_STARTTLS_ENABLE
          value: "false"
        - name: ALARM_MAIL_SMTP_STARTTLS_REQUIRED
          value: "false"
        - name: ALARM_MAIL_TRANSPORT_PROTOCOL
          value: "smtp"
        - name: BATCH_ENABLE
          value: "false"
        - name: BATCH_FLINK_SERVER
          value: "jobmanager"
        - name: BATCH_SERVER_IP
          value: "127.0.0.1"
        - name: CLUSTER_ENABLE
          value: "true"
        - name: CONFIG_SENDUSAGE
          value: "true"
        - name: CONFIG_SHOW_APPLICATIONSTAT
          value: "true"
        - name: JDBC_DRIVERCLASSNAME
          value: "com.mysql.jdbc.Driver"
        - name: JDBC_PASSWORD
          value: "klvchen"
        - name: JDBC_URL
          value: "jdbc:mysql://192.168.10.140:3307/pinpoint?characterEncoding=UTF-8"
        - name: JDBC_USERNAME
          value: "root"
        - name: LOGGING_LEVEL_ROOT
          value: "INFO"
        - name: PINPOINT_ZOOKEEPER_ADDRESS
          value: "zoo1"
        - name: SERVER_PORT
          value: "8079"
        - name: SPRING_PROFILES_ACTIVE
          value: "release,batch"
        ports:
        - containerPort: 9997
          name: http
        - containerPort: 8079
          name: web
        livenessProbe:
          tcpSocket:
            port: 8079
          initialDelaySeconds: 60
          periodSeconds: 180

vim svc.yaml

apiVersion: v1
kind: Service
metadata:
  namespace: pinpoint
  labels:
    app: pinpoint-web
  name: pinpoint-web
spec:
  type: NodePort
  ports:
  - name: http
    port: 9997
    targetPort: 9997
    nodePort: 30097
  - name: web
    port: 8079
    targetPort: 8079
    nodePort: 30079
  selector:
    app: pinpoint-web


kubectl apply -f deployment.yaml 
kubectl apply -f svc.yaml

192.168.10.140:30079

[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-1olgrWLZ-1656905422258)(C:\Users\Administrator\AppData\Roaming\Typora\typora-user-images\image-20220702110251937.png)]

构建测试镜像,进行测试

构建测试镜像

所需要agent的服务器
1、下载agent
mkdir -p /data/demo
cd /data/demo
wget https://github.com/pinpoint-apm/pinpoint/releases/download/v2.1.0/pinpoint-agent-2.1.0.tar.gz

tar zxvf pinpoint-agent-2.1.0.tar.gz
cd /data/demo/pinpoint-agent/profiles/release
cp pinpoint.config  pinpoint.config.ori

2、vim pinpoint.config
把 profiler.transport.grpc.collector.ip 的值指向 pinpoint colector 地址

profiler.transport.grpc.collector.ip=192.168.10.140

3、cd /data/demo
 把 需要的jar包 放到这里，这个jar包的功能会起一个服务，访问 /hello 接口会返回 hello spring

vim DockerFile

FROM openjdk:8u302-slim
RUN ln -sf /usr/share/zoneinfo/Asia/Shanghai  /etc/localtime
ADD demo-0.0.1-SNAPSHOT.jar demo.jar(需要的jar包)
ADD pinpoint-agent-2.1.0 /pinpoint-agent/
COPY docker-entrypoint.sh /
CMD [ "/bin/bash", "/docker-entrypoint.sh" ]

# agentId 最大支持24个字母，必须不同，若是 K8S 多个副本，applicationName 必须一样

vim docker-entrypoint.sh

#!/bin/bash
java -javaagent:/pinpoint-agent/pinpoint-bootstrap-2.1.0.jar  -Dpinpoint.agentId=${HOSTNAME} -Dpinpoint.applicationName=${appName} ${JVM:-Xmx512m -Xms512m} -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/ -Djava.security.egd=file:/dev/./urandom -Duser.timezone=GMT+08 -jar /${appName}.jar

发送给镜像仓库

docker build -t harbor.junengcloud.com/tmp/pinpoint-demo:0.0.11 .
docker push harbor.junengcloud.com/tmp/pinpoint-demo:0.0.11

测试，在master中创建

mkdir -p /data/yaml/default/pinpoint-demo
cd /data/yaml/default/pinpoint-demo

vim deployment.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: demo
spec:
  replicas: 2
  selector:
    matchLabels:
      app: demo
  template:
    metadata:
      labels:
        app: demo
    spec:
      containers:
      - name: demo
        image: harbor.junengcloud.com/tmp/pinpoint-demo:0.0.11(镜像仓库)
        imagePullPolicy: IfNotPresent
        env:
        - name: JVM
          value: "-Xms1024m -Xmx1024m"
        - name: appName
          valueFrom:
            fieldRef:
              fieldPath: metadata.labels['app'] 

kubectl apply -f  deployment.yml

vim svc.yaml

apiVersion: v1
kind: Service
metadata:
  labels:
    app: pinpoint-demo
  name: pinpoint-demo
spec:
  ports:
  - name: http
    port: 8080
    targetPort: 8080
    nodePort: 30079
  selector:
    app: pinpoint-demo
  type: NodePort

kubectl apply -f  svc.yaml

+08 -jar /${appName}.jar


> 发送给镜像仓库

docker build -t harbor.junengcloud.com/tmp/pinpoint-demo:0.0.11 .
docker push harbor.junengcloud.com/tmp/pinpoint-demo:0.0.11




# 测试，在master中创建

mkdir -p /data/yaml/default/pinpoint-demo
cd /data/yaml/default/pinpoint-demo

vim deployment.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
name: demo
spec:
replicas: 2
selector:
matchLabels:
app: demo
template:
metadata:
labels:
app: demo
spec:
containers:
- name: demo
image: harbor.junengcloud.com/tmp/pinpoint-demo:0.0.11(镜像仓库)
imagePullPolicy: IfNotPresent
env:
- name: JVM
value: “-Xms1024m -Xmx1024m”
- name: appName
valueFrom:
fieldRef:
fieldPath: metadata.labels[‘app’]

kubectl apply -f deployment.yml

vim svc.yaml

apiVersion: v1
kind: Service
metadata:
labels:
app: pinpoint-demo
name: pinpoint-demo
spec:
ports:

  • name: http
    port: 8080
    targetPort: 8080
    nodePort: 30079
    selector:
    app: pinpoint-demo
    type: NodePort

kubectl apply -f svc.yaml
林暗森鹿
关注
专栏目录
链路追踪：初探分布式跟踪工具Pinpoint
GIS摆渡人
04-12 325
文章目录一.前言二.架构图1.优点2.Why3.链路跟踪系统的功能三.搭建环境1.Docker环境2.安装JDK3.安装Hbase4.安装pinpoint四.测试收集1.配置Pinpoint-agent2.普通项目部署3.springboot项目部署五.效果演示六.总结参考文章 一.前言 由于工作需要，前段时间抽口研究了一下APM相关技术。 大的互联网公司都有自己的分布式跟踪系统，比如Google的Dapper，Twitter的zipkin，淘宝的鹰眼，新浪的Watchman，京东的Hydra等，当然还有一
【微服务】springcloud集成sleuth与zipkin实现链路追踪
congge
01-21 7201
springcloud集成sleuth与zipkin实现链路追踪
k8s上分布式链路追踪
虎神大帝的博客
10-18 2125
目前最流行的分布式链路追踪系统——SkyWalking 简介： SkyWalking是一款优秀的开源APM（Application Performance Management）系统，它不仅提供了链路追踪，链路分析等分布式追踪功能，还支持性能指标分析、应用和服务依赖性分析、服务拓扑图分析、报警等一系列应用性能监控相关的功能，可以帮助我们有效地定位问题。 而从数据收集上看，SkyWalking支持多种不同的数据来源及格式，包括支持Java、.NET Core、NodeJS、PHP和Python等不同语言
生产环境上k8s避坑指南
findstr的博客
03-24 744
使用环境：阿里云的容器服务-kubernetes 1.ingress使用独立机器部署，配置根据业务量进行评估。前端slb使用按量付费，规格拉到最高（实际按使用量计费）。 2.coreDNS的数量不能过少，一般是业务pod总数的10%。 3.java服务的pod，requests和limits的值必须保持一致。 4.java服务一定要配置合适的JVM参数，尤其注意node如果是高配置机器，需要使用 ...
k8s学习(三十八) 使用OpenTelemetry+jaeger实现链路追踪
最新发布
文若书生的专栏
08-19 950
OpenTelemetry 可以用于从应用程序收集数据。它是一组工具、API 和 SDK 集合，我们可以使用它们来检测、生成、收集和导出遥测数据（指标、日志和追踪），以帮助分析应用的性能和行为。
基SkyWalking实现对k8s集群中微服务的链路追踪
qq_34905631的博客
08-28 1410
2.sykwalking-agent探针的集成到微服务项目（是打成基础镜像里，然后指定参数（configMap中配置java项目的环境变量）运行，还是以sideCar边车的方式运行？第一行的ROM的基础镜像可以使用自己制作的基础镜像也是可以的,前提是需要带有java的环境jre是最小的运行环境或者是装有JDK的环境配置。curl pod的ip:应用的端口,看到如下打印信息是只有health断点暴露了,没有其它的断点暴露。4.私有Hub的安装部署、jenkins的安装部署、jenkins流水线脚本的编写。..
基于SkyWalking实现对k8s集群中微服务的链路追踪分析
最美dee时光的博客
11-21 3015
基于SkyWalking实现对k8s集群中微服务的链路追踪分析背景需求：SkyWalking介绍：实现方式：step1：制作SkyWalking Agent镜像1、准备文件：2、编写skywalking agent的dockerfile文件3、构建镜像step2：编写java服务接入skywalking agent的yamlstep3：执行yaml文件step4：效果图 背景需求： 由于我司之前的服务都是部署在ECS中，对于java微服务的实时链路分析是基于skytwalking agent来做监控的，但是
K8S SWCK SkyWalking全链路跟踪工具安装
crabdave的博客
06-03 1064
K8S SWCK SkyWalking全链路跟踪工具安装
Pinpoint - 应用性能管理(APM)平台实践之部署篇
aibiba0894的博客
02-23 213
0.0 前言 国内的APM行业这两年刚刚起步，但是在国外却比较成熟了，并且由于这两年人力成本的快速提高，国内外涌现了几家非常不错的APM企业，例如APPdynamic，Dynamic，NewRelic等。 我们这里不考虑商业化的实现方案，如何能够提供一种免费的开源实现方案呢？ 下面给大家介绍一个开源的 APM (Application Performance Management/...
全链路追踪 skywalking 和 pinpoint
MoZuoYouDe的博客
11-02 2452
全链路追踪 skywalking 和 pinpoint背景介绍技术对比skywalking搭建1. elasticsearch搭建(*数据源，elasticsearch和mysql选一种即可*)2. mysql搭建3. skywalking 部署4. 探针配置（Agent） 背景介绍      随着业务越来越复杂，企业应用也进入了分布式服务化的阶段，随着模块的不断增多，一次请求可能会涉及到十几个甚至几十个服务的协同处理，那么如何准确快速的定位到线上故障和性能瓶颈，便成
微服务架构之链路追踪原理
永远热泪盈眶 坚持输出
07-16 2226
一、 链路追踪的使用场景 微服务架构是一个分布式架构，它按业务划分服务单元，一个分布式系统往往有很多个服务单元。由于服务单元数量众多，业务的复杂性，如果出现了错误和异常，很难去定位。主要体现在，一个请求可能需要调用很多个服务，而内部服务的调用复杂性，决定了问题难以定位。 所以微服务架构中，必须实现分布式链路追踪，去跟进一个请求到底有哪些服务参与，参与的顺序又是怎样的，从而达到每个请求的步骤清晰可见，出了问题，很快定位。 举几个例子： 在微服务系统中，一个来自用户的请求，请求先达到前端A（如前端界面），然后
分布式链路追踪工具SkyWalking集成Elasticsearch(基于Docker)
01-20
分布式链路追踪工具Apache SkyWalking是一款强大的应用性能管理系统（APM），它专注于提供分布式追踪、服务网格遥测分析以及度量聚合与可视化功能。这款工具适用于微服务架构，帮助开发者和运维人员理解应用程序的...
Pinpoint安装部署
weixin_38037451的博客
01-14 898
Pinpoint安装部署： 1.软件准备： jdk-8u271-linux-x64.tar.gz hbase-1.2.6.1-bin.tar.gz apache-tomcat-9.0.39.tar.gz pinpoint-agent-1.8.4.tar.gz pinpoint-collector-1.8.4.war pinpoint-web-1.8.4.war pinpoint-1.8.4.tar.gz 2.安装JDK 2.1 下载JDK mv jdk-8u271-linux-x64.tar.gz /usr
分布式请求追踪系统分析及实战（k8s部署skywalking）
weixin_42044174的博客
09-29 659
链路追踪，就是将一次分布式请求还原成调用链路，进行日志记录，性能监控并将一次分布式请求的调用情况集中展示。比如各个服务节点上的耗时、请求具体到达哪台机器上、每个服务节点的请求状态等等。
使用Kuboard管理工具k8s容器化部署skywalking实现链路追踪监控
枕上白书的博客
11-25 3249
因为需要使用Nacos作为注册中心，Mysql来存储。需要对skywalking-oap进行自定义。 一、自定义镜像 注意：因为skywalking-oap中没有Mysql驱动包，所以需要下载。 下载mysql驱动Jar包，我使用的是8.0.15版本，下载地址： https://cdn.mysql.com//archives/mysql-connector-java-8.0/mysql-connector-java-8.0.15.zip 新建dockerfile文件，一定要将mysql驱动包放在和dock
实战部署安装 Pinpoint
weixin_33938733的博客
01-08 1135
Pinpoint 安装部署序章pinpoint是开源在github上的一款APM监控工具，它是用Java编写的，用于大规模分布式系统监控。它对性能的影响最小（只增加约3％资源利用率），安装agent是无侵入式的，只需要在被测试的Tomcat中加上3句话，打下探针，就可以监控整套程序了。这篇Blog主要是想记录一下它安装的过程，方便日后查阅。我安装它用到的2台 CentOS6...
一款k8s实时错误监控工具Kubiquity，值得用起来
技术宅，专注云原生、Go、Linux、Java等技术分享，原创文章、效率工具、实战解决方案！关注我，了解互联网动态，学 IT 不迷路
12-24 1766
文章目录它能做什么？它是如何工作的？上手Kubiquity未来要做的 Kubiquity 是一个基于 Electron 的 Kubernetes 健康监控应用程序。它结合了 Kubernetes 命令行工具和 Prometheus 指标服务器，以从集群中获取实时信息。用户可以通过实时跟踪每个集群的事件日志历史以及 CPU 和内存使用情况来跟踪其集群中的异常情况。 它能做什么？ Kubernetes 缺乏强大的错误跟踪。此外， Kubernetes 开发人员需要一个图形用户界面 (GUI) 来与他们的集群进行
链路跟踪工具zipkin——k8s从入门到高并发系列教程（十四）
fanghailiang2016的博客
09-26 1375
使用zipkin 链路跟踪工具，找出时间都消耗在哪了
微服务 一些热门工具：k8s、fabric8、istio、nacos、consul、apollo、orange、kong、pinpoint等链接集合
kwame211的博客
03-10 1078
一站式解决方案： k8s: https://github.com/spring-cloud/spring-cloud-kubernetes 官方文档： https://kubernetes.io/docs/home/?path=users&persona=app-developer&level=foundational fabric8： https://fabri...
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值