Open dvirassamy opened 3 days ago
@makhov I think this boils down to this line: https://github.com/k0sproject/k0smotron/blob/main/internal/controller/controlplane/helper.go#L256-L257
So we do POST
request, shouldn't we always do merge, as in like kubectl apply ...
What happened?
Running successive upgrades on child clusters fails.
Involved Areas
Cluster API integration
What did you expect to happen?
Steps to reproduce
Step 1. Apply manifests with new version definition. The change would trigger an upgrade command
k0smotron successfully runs the k0s upgrade operations.
Step 2 Apply again manifests with new version definition. The change would trigger an upgrade command
k0smotron fails with the following error:
As Autopilot cannot handle two plans with the same name, the upgrade operation fails.
Knowing this limitation of Autopilot, k0smotron should create unique named upgrade plans with unique IDs. This is important to keep the plans history for audit purposes.
k0smotron version
1.2.0
k0s version
*
Anything else we need to know?
No response