You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: