-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Update kuttl to v0.15.0 in the scorecard-test-kuttl image #6401
Update kuttl to v0.15.0 in the scorecard-test-kuttl image #6401
Conversation
Signed-off-by: Andreas Gerstmayr <agerstmayr@redhat.com>
@oceanc80 @everettraven could we move this PR forward? It's blocking us in open-telemetry/opentelemetry-operator#1721 |
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
@oceanc80 @everettraven could we please merge the PR? |
Closing and re-opening to pick up latest CI changes/fixes |
@oceanc80 @everettraven when can we expect this to be released? |
@pavolloffay this should be included in the v1.29.0 release which is currently slated for May 31st |
Great, thanks for merging! |
@everettraven do you know when the container image at https://quay.io/repository/operator-framework/scorecard-test-kuttl?tab=tags&tag=latest gets tagged with a new version? |
@andreasgerstmayr I would have assumed with the 1.29.0 release it would have happened but that doesn't seem to be the case ... Would you mind opening a new issue regarding this so we can track it and get some eyes on it? |
@everettraven sure, I've created #6456. Thanks! |
Description of the change:
Update kuttl to v0.15.0 in the scorecard-test-kuttl image
Motivation for the change:
Fixes cleanup of created resources in kuttl (created resources of a kuttl test will be deleted after the test is run).
This change is especially relevant when using a single namespace for testing (default with this image).
See https://github.com/kudobuilder/kuttl/releases/tag/v0.14.0
Checklist
If the pull request includes user-facing changes, extra documentation is required:
changelog/fragments
(seechangelog/fragments/00-template.yaml
)website/content/en/docs