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
Is your feature request related to a problem? Please describe.
I have to use only one name for an autopilot plan. And I can only have one plan with that same name in the Plan custom resource.
Issue 1 - I do not keep a history of my plans (like jobs)
I need to remove a plan before being to fix a broken plan or applying a new upgrade
I also need to manage the ids to avoid ControlNode annotation conflicts (the latter keeps track of previous operations).
For example adding a new plan with the same id as a previously successful plan would cause the newly added plan status to directly become successful without actually applying the change.
Describe the solution you would like
Define a flexible plan name (standard kube naming convention)
Keep history of the plans (like jobs) (for failed and successful)
Improve ControlNode annotations
Get better monitoring of running plans, events and status of plans
Describe alternatives you've considered
No response
Additional context
Users are confused on how to use plans, where to look when you have issues and how to fix the different objects.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I have to use only one name for an autopilot plan. And I can only have one plan with that same name in the Plan custom resource.
I also need to manage the ids to avoid ControlNode annotation conflicts (the latter keeps track of previous operations).
For example adding a new plan with the same id as a previously successful plan would cause the newly added plan status to directly become successful without actually applying the change.
Describe the solution you would like
Describe alternatives you've considered
No response
Additional context
Users are confused on how to use plans, where to look when you have issues and how to fix the different objects.
The text was updated successfully, but these errors were encountered: