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

feat: Make sure each controller removes undesired state on update #205

Open
4 tasks
portly-halicore-76 opened this issue Dec 11, 2024 · 0 comments
Open
4 tasks
Labels

Comments

@portly-halicore-76
Copy link
Contributor

portly-halicore-76 commented Dec 11, 2024

Feature Request

Describe the Feature Request

This is a request to go over each controllers logic. Each controller should, on updates from the Paas(Ns), determine the current state, determine the desired state, remove unused resources and create desired resources. We know at least for Groups this isn't implemented, meaning, "undesired" groups ain't deleted once a Paas is deleted. Might apply to more controllers.

This relates also to the PaasConfig resource. When changes are made to the active PaasConfig, the Paas(Ns)'es are reconciled again, as the desired state of dependant resources might have changed. Certainly in that case, obsolete resources must be removed.

Describe Preferred Solution

  • If possible, make should each created resource has an owner reference to the Paas desiring it
  • On update / delete of a Paas(Ns), list current resources with the object to this Paas
  • On update, calculate desired state of dependant resources
  • On update / delete, remove obsolete existing resources
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant