Closed Nello-Angelo closed 1 year ago
i have also loki stack and i collect logs with vector. With vector i have not such problem
apiVersion: apps/v1
kind: DaemonSet
metadata:
name: vector
namespace: loki
labels:
app.kubernetes.io/component: Agent
app.kubernetes.io/instance: vector
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: vector
app.kubernetes.io/version: 0.31.0-distroless-libc
helm.sh/chart: vector-0.23.0
k8slens-edit-resource-version: v1
annotations:
deprecated.daemonset.template.generation: '7'
meta.helm.sh/release-name: vector
meta.helm.sh/release-namespace: loki
spec:
selector:
matchLabels:
app.kubernetes.io/component: Agent
app.kubernetes.io/instance: vector
app.kubernetes.io/name: vector
template:
metadata:
creationTimestamp: null
labels:
app.kubernetes.io/component: Agent
app.kubernetes.io/instance: vector
app.kubernetes.io/name: vector
vector.dev/exclude: 'true'
annotations:
checksum/config: ef8d6179360a03ee10ec8839058147a4c46573f4cd62a514aa11ec56596a4a74
kubectl.kubernetes.io/restartedAt: '2023-08-09T17:20:59Z'
linkerd.io/inject: enabled
spec:
volumes:
- name: config
projected:
sources:
- configMap:
name: vector
defaultMode: 420
- name: data
hostPath:
path: /var/lib/vector
type: ''
- name: var-log
hostPath:
path: /var/log/
type: ''
- name: var-lib
hostPath:
path: /var/lib/
type: ''
- name: procfs
hostPath:
path: /proc
type: ''
- name: sysfs
hostPath:
path: /sys
type: ''
containers:
- name: vector
image: timberio/vector:0.31.0-distroless-libc
args:
- '--config-dir'
- /etc/vector/
ports:
- name: api
containerPort: 8686
protocol: TCP
env:
- name: VECTOR_SELF_NODE_NAME
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: spec.nodeName
- name: VECTOR_SELF_POD_NAME
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: metadata.name
- name: VECTOR_SELF_POD_NAMESPACE
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: metadata.namespace
- name: PROCFS_ROOT
value: /host/proc
- name: SYSFS_ROOT
value: /host/sys
- name: VECTOR_LOG
value: info
resources:
limits:
cpu: '10'
memory: 10Gi
requests:
cpu: 200m
memory: 256Mi
volumeMounts:
- name: data
mountPath: /var/local/lib/vector/
- name: config
readOnly: true
mountPath: /etc/vector/
- name: var-log
readOnly: true
mountPath: /var/log/
- name: var-lib
readOnly: true
mountPath: /var/lib
- name: procfs
readOnly: true
mountPath: /host/proc
- name: sysfs
readOnly: true
mountPath: /host/sys
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
imagePullPolicy: IfNotPresent
restartPolicy: Always
terminationGracePeriodSeconds: 60
dnsPolicy: ClusterFirst
serviceAccountName: vector
serviceAccount: vector
securityContext: {}
schedulerName: default-scheduler
tolerations:
- operator: Exists
effect: NoSchedule
updateStrategy:
type: RollingUpdate
rollingUpdate:
maxUnavailable: 1
maxSurge: 0
revisionHistoryLimit: 10
The problem with the node-exporter DaemonSet is that it uses host networking. The proxy is designed to work under a pod's networking namespace, so the proxy-injector will ignore any workload that uses host networking.
ok thanks
any workaround?
No sorry, i dont no, host netns needs exporter
What is the issue?
can`t inject node-exporter
How can it be reproduced?
install node-exporter from chart
Logs, error output, etc
-
output of
linkerd check -o short
-
Environment
kubernetes - 1.25.8 OS - debian 11 linkerd - stable-2.13.5
Possible solution
-
Additional context
-
Would you like to work on fixing this bug?
no