Currently when creating a new rollout on saving settings on a project the backend will create a completely new rollout instance inside the cluster. This behaviour is kinda bad because it will recreate all resources.
The better option would be to just edit the rollout specs on the running rollout inside the cluster and save the json/yaml in pocketbase.
The smoothest one to implement this is in the backend not frontend.
Currently when creating a new rollout on saving settings on a project the backend will create a completely new rollout instance inside the cluster. This behaviour is kinda bad because it will recreate all resources. The better option would be to just edit the rollout specs on the running rollout inside the cluster and save the json/yaml in pocketbase.
The smoothest one to implement this is in the backend not frontend.