-
Notifications
You must be signed in to change notification settings - Fork 242
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
Upgrade kubearchvie to v0.4.0 #4929
Conversation
Hi @mafh314. Thanks for your PR. I'm waiting for a redhat-appstudio member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
/approve |
/approve |
/lgtm |
@hugares how can make this progress? |
/retest |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mafh314, rh-hemartin, skoved 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 |
There is a bogus check (Red Hat Konflux) that I do not know how to get rid of when PR is opened by someone that is not a member of the org... Merging this one |
Updating KubeArchive from 0.3.0 to 0.4.0. I deleted from the patch the resource quota for the sink and api component since that is part of the KubeArchive deployment yaml files (introduced by the OpenTelemetry instrumentation). The other changes are related to the yaml lint.