-
Notifications
You must be signed in to change notification settings - Fork 547
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
[wip]rebase: adopt logging framework change and update to kube 1.26 #3572
Conversation
Was the first commit required to get second commit to work ? The reason for the first commit of e2elog to framework.Log change is not clear to me. |
This pull request now has conflicts with the target branch. Could you please resolve conflicts and force push the corrected changes? 🙏 |
bbd0b34
to
05d1cd7
Compare
This pull request now has conflicts with the target branch. Could you please resolve conflicts and force push the corrected changes? 🙏 |
the logging is part of the core framework and this commit address the same. Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
this commit update the kube dependencies. Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
This pull request now has conflicts with the target branch. Could you please resolve conflicts and force push the corrected changes? 🙏 |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks if no further activity occurs. Thank you for your contributions. |
This pull request has been automatically closed due to inactivity. Please re-open if these changes are still required. |
This commit update the dependency to 1.26.0 version along with
other client modules.
log framework package is part of core framework with this kube version update.
Signed-off-by: Humble Chirammal hchiramm@redhat.com