Skip to content
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: add finalizers to cleanup cluster scoped resources on stack dele… #608

Merged

Conversation

jan--f
Copy link
Collaborator

@jan--f jan--f commented Oct 28, 2024

…tion

Fixes: COO-495

@jan--f jan--f requested a review from a team as a code owner October 28, 2024 15:55
@jan--f jan--f requested review from danielmellado and JoaoBraveCoding and removed request for a team October 28, 2024 15:55
Copy link

openshift-ci bot commented Oct 28, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jan--f

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jan--f jan--f force-pushed the finalizer-cluster-scoped-resources branch from 3cb25f0 to 7115cc7 Compare October 29, 2024 11:48
logger.V(6).Info("skipping reconcile since object is already schedule for deletion")
logger.V(6).Info("removing cluster scoped resources")

reconcilers := stackComponentCleanup(ms)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just a nit over here, if we have the prometheus and the alertamanager names, why not adding that also as a log? It may be useful when debugging. Otherwise lgtm!

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is just an info log. In line 158 an error is logged in case something goes wrong, that'll include the resource name that creates an error. Is that what you're after?

Not sure we should log 6 resource names on the happy path.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nvm, mistook the 'Info' for 'Err' in my mind, LGTM then, thanks!

@danielmellado
Copy link
Contributor

danielmellado commented Oct 29, 2024 via email

@danielmellado
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Oct 29, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit b243203 into rhobs:main Oct 29, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants