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

Delete manifestwork for application namespace #1381

Merged
merged 3 commits into from
Sep 6, 2024

Conversation

abhijeet219
Copy link
Member

@abhijeet219 abhijeet219 commented May 8, 2024

Changes:

  • Update open-cluster-management to version v0.13.0
  • Delete namespace manifestwork for applications
  • Unit test changes to verify deletion of namespace manifestwork

The changeset includes a new DeleteNamespaceManifestWork() func to delete the manifestwork for namespace. It first checks if the mw.Spec has delete option or if it already has a DeletionTimestamp. Accordingly, it proceeds to delete the
namespace manifestwork.
Also introduces updating of the namespace manifestwork with the deleteOption and propogationPolicy of type orphan, whenever the createOrUpdateNamespaceManifest() func is called.

Fixes: Bug 2059669

controllers/util/mw_util.go Outdated Show resolved Hide resolved
@abhijeet219 abhijeet219 force-pushed the mw-namespace branch 3 times, most recently from 43b930d to e357612 Compare May 9, 2024 11:02
@abhijeet219 abhijeet219 force-pushed the mw-namespace branch 2 times, most recently from 721c578 to c1e5699 Compare May 10, 2024 11:37
controllers/drplacementcontrol.go Outdated Show resolved Hide resolved
controllers/drplacementcontrol_controller.go Outdated Show resolved Hide resolved
controllers/drplacementcontrol_controller_test.go Outdated Show resolved Hide resolved
controllers/drplacementcontrol_controller.go Outdated Show resolved Hide resolved
controllers/drplacementcontrol_controller.go Outdated Show resolved Hide resolved
controllers/drplacementcontrol_controller.go Outdated Show resolved Hide resolved
@abhijeet219 abhijeet219 force-pushed the mw-namespace branch 4 times, most recently from 4154453 to e634d18 Compare May 14, 2024 15:00
@abhijeet219 abhijeet219 force-pushed the mw-namespace branch 2 times, most recently from c4bc3bc to dda721a Compare June 5, 2024 05:14
@abhijeet219 abhijeet219 force-pushed the mw-namespace branch 5 times, most recently from 29ed404 to b8735a2 Compare July 16, 2024 11:30
@abhijeet219 abhijeet219 marked this pull request as ready for review July 22, 2024 05:04
@abhijeet219 abhijeet219 force-pushed the mw-namespace branch 4 times, most recently from f0bdf1b to 4ea8d31 Compare August 12, 2024 09:27
@abhijeet219 abhijeet219 force-pushed the mw-namespace branch 3 times, most recently from f2ca445 to 776428d Compare August 18, 2024 16:25
Copy link
Member

@ShyamsundarR ShyamsundarR left a comment

Choose a reason for hiding this comment

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

@abhijeet219 please rebase to latest main, and we can merge. Change looks good.

The one nit I have is on the function name, if that can be addressed as part of the rebase it would be nice. Thanks!

internal/controller/drplacementcontrol_controller.go Outdated Show resolved Hide resolved
The changeset includes a new DeleteNamespaceManifestWork() func,
which first checks if the mw.Spec has delete option or if it already
has a DeletionTimestamp. Accordingly, it proceeds to delete the
namespace manifestwork.
It also updates the namespace manifestwork with the deleteOption and
propogationPolicy of type orphan, whenever the createOrUpdateNamespaceManifest()
func is called.

Fixes: [Bug 2059669](https://bugzilla.redhat.com/show_bug.cgi?id=2059669)
Signed-off-by: Abhijeet Shakya <[email protected]>
@ShyamsundarR ShyamsundarR merged commit 91ebfba into RamenDR:main Sep 6, 2024
19 of 20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants