🐛 cleanup: eliminate log spam when using S3 secrets#4667
🐛 cleanup: eliminate log spam when using S3 secrets#4667k8s-ci-robot merged 1 commit intokubernetes-sigs:mainfrom
Conversation
|
Hi @thefirstofthe300. Thanks for your PR. I'm waiting for a kubernetes-sigs 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. DetailsInstructions 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/test-infra repository. |
212ce90 to
16eba48
Compare
16eba48 to
0e6b5dd
Compare
0e6b5dd to
ca2cae6
Compare
|
/ok-to-test |
|
/test ? |
|
@vincepri: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
DetailsIn 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 kubernetes/test-infra repository. |
|
/test pull-cluster-api-provider-aws-e2e |
AndiDog
left a comment
There was a problem hiding this comment.
One compatibility blocker. Rest looks fine.
For upcoming feature kubernetes-sigs/cluster-api-provider-aws#4667
For upcoming feature kubernetes-sigs/cluster-api-provider-aws#4667
For upcoming feature kubernetes-sigs/cluster-api-provider-aws#4667
ca2cae6 to
abb23b7
Compare
|
/retest |
abb23b7 to
0be00ee
Compare
|
/test pull-cluster-api-provider-aws-e2e |
|
/approve cc @AndiDog for another review |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Ankitasw The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
/kind cleanup
Currently, the S3 object store generates a large amount of log spam during reconciliation. Objects are stated to be deleting regardless of objects already being deleted.
Example:
Release note: