[Feature] resourcekeeper provides control capability on the application level

oeular commented 2 years ago

The main implementation of the resource management logic locates at pkg/resourcekeeper. The ResourceKeeper takes charge of the dispatching, tracking, and recycling of all resources.

Dispatch: First record resources in ResourceTracker, then apply resources. Depending on the life-cycle of resources, either Versioned ResourceTracker or Root ResourceTracker will be used.
Delete: First mark resources as deleted in ResourceTracker, then delete resources.
StateKeep: Ranging over all managed resources in the latest Versioned ResourceTracker and Root ResourceTracker, re-apply those resources.
GarbageCollect: Mark outdated or unused ResourceTrackers as deleted and garbage-collect their managed resources. Details will be delivered below.

we want the capacity of resourcekeeper can work on or not work on some specified application when we convert the k8s objects in the managed clusters to OAM application in the hub cluster. Work on when converting goes well. Not work on when errors of converting happen.

Somefive commented 2 years ago

Capacity of resourcekeeper? Do you mean capability of resourcekeeper? Or the size of the resourcekeeper?

oeular commented 2 years ago

@Somefive You're right, I mean the capability of resourcekeeper.

Somefive commented 2 years ago

How do you do the conversion? External CLI tools or operators on server?

Is there any way for KubeVela controller to know whether the conversion goes well or not?

kubevela / kubevela

[Feature] resourcekeeper provides control capability on the application level #4394