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.

Sign up for GitHub

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

Jump to bottom

Handling Cluster Scoped Resources #4

Closed
csviri opened this issue Jan 2, 2024 · 1 comment · Fixed by #92
Closed

Handling Cluster Scoped Resources #4

csviri opened this issue Jan 2, 2024 · 1 comment · Fixed by #92
Milestone
0.x

Comments

@csviri
Copy link
Owner

csviri commented Jan 2, 2024

Owner References are not working for resources which are cluster scoped (by design in k8s). Those needs to be explicitly deleted.
This is already supported in DependentResources, just it needs to be detected which resource is cluster scoped and which is not.
@csviri csviri added this to the 0.2.0 milestone Jan 2, 2024
@csviri csviri changed the title Handling Cluster Scoped Dependents Handling Cluster Scoped Resources and Resources from Different Namespace Mar 31, 2024
@csviri csviri changed the title Handling Cluster Scoped Resources and Resources from Different Namespace Handling Cluster Scoped Resources Mar 31, 2024
@csviri
Copy link
Owner Author

csviri commented Mar 31, 2024

Maybe namespace should be simply mandatory to specify for non cluster scoped resources

@csviri csviri linked a pull request May 1, 2024 that will close this issue
feat: support cluster scoped and different namespace resources #92
Merged
@csviri csviri closed this as completed in #92 May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.x
Development

Successfully merging a pull request may close this issue.

feat: support cluster scoped and different namespace resources csviri/kubernetes-glue-operator
1 participant
@csviri