This is a clone of issue OCPBUGS-3084. The following is the description of the original issue:
—
Upstream Issue: https://github.com/kubernetes/kubernetes/issues/77603
Long log lines get corrupted when using '--timestamps' by the Kubelet.
The root cause is that the buffer reads up to a new line. If the line is greater than 4096 bytes and '--timestamps' is turrned on the kubelet will write the timestamp and the partial log line. We will need to refactor the ReadLogs function to allow for a partial line read.
apiVersion: v1
kind: Pod
metadata:
name: logs
spec:
restartPolicy: Never
containers:
- name: logs
image: fedora
args:
- bash
- -c
- 'for i in `seq 1 10000000`; do echo -n $i; done'
kubectl logs logs --timestamps
- blocks
-
OCPBUGS-3174 Pod logs: Long lines are corrupted when using timestamps=true
- Closed
- clones
-
OCPBUGS-3084 Pod logs: Long lines are corrupted when using timestamps=true
- Closed
- is blocked by
-
OCPBUGS-3084 Pod logs: Long lines are corrupted when using timestamps=true
- Closed
- is cloned by
-
OCPBUGS-3174 Pod logs: Long lines are corrupted when using timestamps=true
- Closed
- links to