dashboard
dashboard copied to clipboard
kubermatic
Make Provider Preset Deletion Possible
Why?
Not being able to delete provider presets and having no information as to why it's not possible is confusing and the fact that deletion is not possible will cause a build up of unused useless provider presets
How?
- Make a check "is any cluster using this? -> No -> Allow Deletion"
- (if possible) "is any cluster using this? -> Yes -> Give migration to another preset option -> Offer to delete preset after migration" OR
- is any cluster using this? -> No -> Grey out deletion option and show reason as to why it's not possible in a tooltip OR make it possible to open a delete modal and say why it's not possible in the modal, with both options ideally showing which clusters use the preset so the user can manually change the clusters and be able to delete the provider preset after making it unused
The main issue here is with the API and how presets are handled after creation and when they are used by the cluster. The issue should be created in the API. From the UI side using the delete endpoint is extremely simple, API on the other hand will be very complex to handle.
We are not sure if we need to keep the connection between cluster or template with the preset @shaase-ctrl we would like to discuss it next sig UI/API meeting
We should disconnect a preset from having multiple providers, then we can start with referencing which preset is used in which project
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kubermatic-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.