Skip to content

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

Description

@portly-halicore-76

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions