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
By design, Playbook has a lifecycle, from creation, initialization, compilation build, deployment, running to destruction.
Currently, we need to implement a new controller to perform periodic resource recovery (destruction) of Playbook. The following is a technical description:
The administrator can set a resource recovery duration, such as 2 weeks (default);
this duration is annotated on each Playbook resource definition;
Timeout Controller periodically scans for Playbooks that are about to expire and performs a series of actions, such as sending reminder emails or notifications (e.g. via Slack) 3 days or 2 days before the expiration date, and performs Playbook deletion on the same day;
Additional consideration is given to support Webhook notification of events in the future;
Additional information:
The Kubernetes platform itself has a ttl-controller that is only used for Job resource recovery, the code should be in the K8s repository and can also be viewed as a reference
By design, Playbook has a lifecycle, from creation, initialization, compilation build, deployment, running to destruction.
Currently, we need to implement a new controller to perform periodic resource recovery (destruction) of Playbook. The following is a technical description:
Reference:
Note: Contributors are requested to provide technical design solutions and implementation plans in the comments, as we need to communicate more fully.
The text was updated successfully, but these errors were encountered: