-
Notifications
You must be signed in to change notification settings - Fork 59
Fix component output logs in e2e workflow #456
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
Fix component output logs in e2e workflow #456
Conversation
88ae81f to
4184a77
Compare
|
Updated commit to use the right cluster name context. |
4184a77 to
7a6d3e1
Compare
Srihari1192
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
7a6d3e1 to
6530593
Compare
Bobbins228
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Bobbins228, Srihari1192, sutaakar The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Issue link
Previously, the artifact logs failed to be generated as they are being requested by the

sdk-userwith limited permissions:What changes have been made
After the e2e run completes, the context is switched back to cluster-admin.
Verification steps
Output logs in e2e workflow should show no errors.
Checks