You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run kubectl create -f test.yaml to create a taskrun
Run k get pod | grep test to the pod id
Run kl pod/testlvv64-pod, there is no any log. but the doc says Once stdoutConfig.path or stderrConfig.path is specified, the corresponding output stream will be duplicated to both the given file and the standard output stream of the container, so users can still view the output through the Pod log API.
Expected Behavior
Should have log
Actual Behavior
No logs
Steps to Reproduce the Problem
kubectl create -f test.yaml
to create a taskrunk get pod | grep test
to the pod idkl pod/testlvv64-pod
, there is no any log. but the doc saysOnce stdoutConfig.path or stderrConfig.path is specified, the corresponding output stream will be duplicated to both the given file and the standard output stream of the container, so users can still view the output through the Pod log API.
Additional Info
Kubernetes version:
Output of
kubectl version
:Tekton Pipeline version:
Output of
tkn version
orkubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'
the test.yaml file
The text was updated successfully, but these errors were encountered: