-
Notifications
You must be signed in to change notification settings - Fork 413
OCPBUGS-59311: oc adm must-gather: Perform cleanup on signal received #2062
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
base: main
Are you sure you want to change the base?
Conversation
@tchap: This pull request references Jira Issue OCPBUGS-59311, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
/jira refresh |
@tchap: This pull request references Jira Issue OCPBUGS-59311, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: tchap The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The command now removes any temporary resources on signal received, i.e. the whole temp namespace generally, or just the pods in case --run-namespace is specified. To be able to implement this, kubectl logs has been pulled in as pkg/cli/internal/logs. This is needed for now to be able to interrupt logs streaming as LogOptions.RunLogsContext is not yet available in v33. We can remove kubectl logs copy in the next release and use the relevant function, though, so added a TODO.
2338818
to
71dd73e
Compare
Ok, let's wait until kubernetes/kubernetes#133067 is merged and available. We will revisit the PR then. |
@tchap: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
/hold until the upstream PR and function becomes available. |
The command now removes any temporary resources on signal received,
i.e. the whole temp namespace generally, or just the pods in case
--run-namespace
is specified.Since there is no way to interrupt log streaming in
kubectl
currently,I ended up just pulling
kubectl logs
in as an internal package and addingRunLogsContext
.I sent a PR to add the method into upstream as well, but that will be only available
as we rebase onto the next release.
Let me know if you have any better idea. I did that because some
of the methods on
LogOptions
are private, so I couldn't reimplementthe logic without basically rewriting the while thing anyway.