-
Notifications
You must be signed in to change notification settings - Fork 644
[v25.1.x] rpk: improve rpk debug bundle assumptions in k8s environments #26164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v25.1.x] rpk: improve rpk debug bundle assumptions in k8s environments #26164
Conversation
For Mac users. We won't need this now that we have upgraded to Bazel 8. (cherry picked from commit 17cbc78)
We had build tags for the other files already. We previously missed the build tag on this file. (cherry picked from commit 1dc1a5e)
rpk debug bundle works on a best-effort basis. It always tries to return a bundle—even if some steps (like logs or resource collection) fail. Sometimes, is because the system is unhealthy leading to expected errors. Seeing errors doesn't mean the bundle is useless. This change aims to make this clearer for the user. (cherry picked from commit 066732a)
If --namespace is not provided, fallback to $NAMESPACE, then /var/run/secrets/kubernetes.io/serviceaccount/namespace, and finally default to "redpanda". This avoids hardcoding and better supports various deployment environments. (cherry picked from commit adb9d38)
When collecting a debug bundle from a k8s environment, we now: - Log a warning if admin addresses cannot be retrieved from the k8s API. - Use the union of the profile-defined admin addresses and those returned by the k8s API. - Fall back to 127.0.0.1 if no addresses are available from either source. - Log the final list of admin addresses used. This improves reliability and visibility in environments with incomplete or misconfigured cluster info. (cherry picked from commit 939e1ba)
We will stop assuming `redpanda` to be the default container name. Instead we are going to fetch the logs of all containers and initContainers in the namespace/pod. Logs will still be stored under logs/ (cherry picked from commit d66c6b0)
Retry command for Build#66072please wait until all jobs are finished before running the slash command
|
CI test resultstest results on build#66072
|
/ci-repeat 1 |
Backport of PR #26091