Details
-
Bug
-
Status: Patch Available
-
Minor
-
Resolution: Unresolved
-
2.7.3
-
None
-
None
Description
Currently, when we access a container's logfile (via /ws/v1/node/containerlogs/) we can only get the full content, not a specified range.
Support for the Range: header would improve this, special when dealing with big files that need to be tailed or streamed, i.e.:
curl -H 'Range: bytes=10240' \ http://node:8042/ws/v1/node/containerlogs/container_XXX/stdout