iLogtail使用入门-K8S环境快照采集到SLS
2025-08-06 12:16:31
max-bytes-per-sec: "20971520"
send-requests-concurrency: "20"
2.计算alicloud-log-config.yaml的sha256 hash,并校对ilogtail的DaemonSet YAML。
$ sha256sum alicloud-log-config.yaml
f370df37916797aa0b82d709ae6bfc5f46f709660e1fd28bb49c22da91da1214 alicloud-log-config.yaml
$ vim logtail-daemonset.yaml
在Vim中的嵌入如下以下内容并留有(注意,重写注释中的高亮的报文,21、25行)。
apiVersion: apps/v1
kind: DaemonSet
metadata:
name: logtail-ds
namespace: kube-system
labels:
k8s-app: logtail-ds
spec:
selector:
matchLabels:
k8s-app: logtail-ds
updateStrategy:
type: RollingUpdate
template:
metadata:
labels:
k8s-app: logtail-ds
kubernetes.io/cluster-service: "true"
version: v1.0
annotations:
checksum/config: f370df37916797aa0b82d709ae6bfc5f46f709660e1fd28bb49c22da91da1214 #必须重写为alicloud-log-config.yaml的hash
spec:
containers:
- name: logtail
image: registry.cn-wulanchabu.aliyuncs.com/log-service/logtail:latest #可以重写为距离k8s集群最近的地域
resources:
limits:
cpu: 2
memory: 1024Mi
requests:
cpu: 100m
memory: 256Mi
livenessProbe:
httpGet:
path: /liveness
port: 7953
scheme: HTTP
initialDelaySeconds: 30
periodSeconds: 60
securityContext:
privileged: true
env:
- name: HTTP_PROBE_PORT
value: "7953"
- name: "ALIYUN_LOGTAIL_CONFIG"
valueFrom:
configMapKeyRef:
name: alibaba-log-configuration
key: log-config-path
- name: "ALIYUN_LOGTAIL_USER_ID"
valueFrom:
configMapKeyRef:
name: alibaba-log-configuration
key: log-ali-uid
- name: "ALIYUN_LOGTAIL_USER_DEFINED_ID"
valueFrom:
configMapKeyRef:
name: alibaba-log-configuration
key: log-machine-group
- name: "ALICLOUD_LOG_ACCESS_KEY_ID"
valueFrom:
configMapKeyRef:
name: alibaba-log-configuration
key: access-key-id
- name: "ALICLOUD_LOG_ACCESS_KEY_SECRET"
valueFrom:
configMapKeyRef:
name: alibaba-log-configuration
key: access-key-secret
- name: "ALICLOUD_LOG_DOCKER_ENV_CONFIG"
value: "true"
- name: "ALICLOUD_LOG_ECS_FLAG"
value: "false"
- name: "ALICLOUD_LOG_DEFAULT_PROJECT"
valueFrom:
configMapKeyRef:
name: alibaba-log-configuration
key: log-project
- name: "ALICLOUD_LOG_ENDPOINT"
valueFrom:
configMapKeyRef:
name: alibaba-log-configuration
key: log-endpoint
- name: "ALICLOUD_LOG_DEFAULT_MACHINE_GROUP"
valueFrom:
configMapKeyRef:
name: alibaba-log-configuration
key: log-machine-group
- name: "ALIYUN_LOG_ENV_TAGS"
value: "_node_name_|_node_ip_"
- name: "_node_name_"
valueFrom:
fieldRef:
fieldPath: spec.nodeName
- name: "_node_ip_"
valueFrom:
fieldRef:
fieldPath: status.hostIP
# resource limit for logtail self process
- name: "cpu_usage_limit"
valueFrom:
configMapKeyRef:
name: alibaba-log-configuration
key: cpu-core-limit
- name: "mem_usage_limit"
valueFrom:
configMapKeyRef:
name: alibaba-log-configuration
key: mem-limit
- name: "max_bytes_per_sec"
valueFrom:
configMapKeyRef:
name: alibaba-log-configuration
key: max-bytes-per-sec
- name: "send_request_concurrency"
valueFrom:
configMapKeyRef:
name: alibaba-log-configuration
key: send-requests-concurrency
volumeMounts:
- name: sock
mountPath: /var/run/
- name: root
mountPath: /logtail_host
readOnly: true
mountPropagation: HostToContainer
terminationGracePeriodSeconds: 30
tolerations:
- operator: "Exists"
hostNetwork: true
dnsPolicy: "Default"
volumes:
- name: sock
hostPath:
path: /var/run/
- name: root
hostPath:
path: /
3.技术的发展YAML装配,始创ConfigMap和DaemonSet。
$ kubectl apply -f alicloud-log-config.yaml
configmap/alibaba-log-configuration created
$ kubectl apply -f logtail-daemonset.yaml
daemonset.apps/logtail-ds created
4.等待1分钟,检查DeamonSet是否正常运行
$ kubectl get -f logtail-daemonset.yaml
这个时候的设备应该打印造出类似以下的谣言,代表内置事与愿违
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
logtail-ds 3 3 3 3 3 2m1s
上报快照并转发 始创一个用于持续生成快照的Pod。$ vim demo-pod.yaml
在Vim中的嵌入如下以下内容并留有(注意,可能会并不需要重写注释中的高亮的报文,8-9行)。
apiVersion: v1
kind: Pod
metadata:
labels:
name: demo-pod
name: demo-pod
spec:
# imagePullSecrets: # Comment out to enable specific image pull secret
# - name: myregistrykey # repleace it to specific registry key containers
containers:
- image: busybox
imagePullPolicy: IfNotPresent
name: demo-pod
command: ["/bin/sh"]
args: ["-c", "while true; do echo $(date)>>/tmp/demo.log; sleep 10; done"]
resources: {}
securityContext:
capabilities: {}
privileged: false
terminationMessagePath: /dev/termination-log
dnsPolicy: ClusterFirst
restartPolicy: Always
技术的发展YAML装配,始创Pod
$ kubectl apply -f demo-pod.yaml
pod/demo-pod created
2.回到Web的设备,点选装配已完成技术的发展程序的“转发快照”跳转到快照转发技术的发展程序。点选首页左面的“方是”屏幕,选中的logstore,点选“嘴唇”屏幕,在左面造出现的“购物演示”侧边右上角的无论如何修正Shard和小时覆盖范围,点选演示转发上报的快照。
What's Next你可以转到下一节学习《ilogtail可用基础知识-iLogtail本地部署提议》
明了托盘采自数学模型《通过DaemonSet-的设备方式采自托盘标准输造出》
也可以学习ilogtail采自的越来越多用法:
通过DaemonSet-的设备方式采自托盘评注快照 采自托盘快照 如何赚取托盘的Label和环境变量本文为阿里云原创以下内容,未经受限制不得刊发。
。北京男科医院哪家最好北京看白癜风哪家医院专业
山东妇科医院哪个好
北京妇科医院排名
肠胃不舒服怎么缓解
止咳化痰的药哪个效果好
急支糖浆是什么药?
风热感冒咳嗽吃什么药止咳化痰效果好
儿科综合
小儿便秘怎么办
-
如果一个人不爱你了,就这样处置吧,别再委屈自己了!
心公事情这件公事,不是你希望了,就时会有好的结果。 片子《从你的迄今为止一路上》中,猪头回去头追着消逝的出租车,回去头哭着大声:“没人有人你,我怎么日常生活。”可他没人拦住仙鹤的离
2025-08-23 00:16:35
-
性格明确,聪明伶俐,对于窘境,常常自主进逼,绝处逢生的四属相
干支飞龙的朋友在在有创业观念或理财动静的鸡仔可以在多明白一下相关的具体内容,可能时会有人出来扶助你概述的研究个中会的必先,使你获取有所增加的某种程度与前途,不约而同您职场的尾端马上驶出了,孔洞的
2025-08-23 00:16:35
-
“乐视最后的机皇”,都已发布的LEX850深度评测
灰白加在彩色双摄,下方则是双人眼变焦。双摄一小有灰色的以变焦为里心的半圆形图层,在光线照耀下但会形扫描图里一样的真实感。而下方的双人眼变焦则有别于的是与尾翼同色的穿孔点缀条建筑设计,两块操纵器在同一个
2025-08-23 00:16:35
-
普利制造用GDR替代定增,再融资呈现新常态?
公司GDR面世旋律有所加快,但一位买方专业人士并不知道路透社,由于GDR生产并成本一般,买方配售GDR后一般才会在兑回锁就其期满后兑换并成A股证券再进行结算。以中会国太保为例,公开资讯看出,该
2025-08-23 00:16:35
-
国产游戏版号时隔8个月重启,游戏板块参与者走强
国产RPG版号时隔8个月重启,RPG板块集体走强 4月11日晚,国家新闻出版署公布了“2022年4月份国产网络RPG审批文档”,共45款RPG拿回批在RPG版号,相关RP
2025-08-23 00:16:35