If one enables PodLogsQuerySplitStreams and aims to access logs without stream, a validation error occurs #128709
Labels
kind/bug
Categorizes issue or PR as related to a bug.
kind/failing-test
Categorizes issue or PR as related to a consistently or frequently failing test.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
sig/node
Categorizes an issue or PR as relevant to SIG Node.
Milestone
Comments
k8s-ci-robot
added
needs-sig
|
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/sig node |
k8s-ci-robot
added
sig/node
|
The PR that caused this is #127360. |
|
/priority critical-urgent |
k8s-ci-robot
added
the
priority/critical-urgent
dims
added
the
kind/failing-test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
We saw this in our alpha jobs.
https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-kind-alpha-features/1854662086911594496
https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/128680/pull-e2e-gci-gce-alpha-enabled-default/1854616736976867328
What did you expect to happen?
One should be able to run the following command with this feature gate on:
How can we reproduce it (as minimally and precisely as possible)?
Start a cluster with PodLogsQuerySplitStreams enabled.
Anything else we need to know?
No response
Kubernetes version
1.32
Cloud provider
NA
OS version
No response
Install tools
Container runtime (CRI) and version (if applicable)
Related plugins (CNI, CSI, ...) and versions (if applicable)
The text was updated successfully, but these errors were encountered: