Open iainlane opened 1 year ago
--force
is mapped inside of tanka to mean --force-conflicts
when used along with the server-side apply strategy 👍
So basically the outcome of that issue should be an additional to the environment spec that controls the force
flag?
Not sure. Could server
imply using --force
all the time and then you don't need to set two flags to use server
in this configuration (with flux)?
We have Flux (v2) managing our deployments.
We wanted to try server-side applies which are supported by tanka. Since my environment here is an inline environment I added
tanka.environment.withApplyStrategy('server')
to itstanka.environment.new()
call. Then runningtk apply
failed like this:Same would probably happen in the
spec.json
instead.I didn't try but
tk apply --force
would probably have worked. Maybe an extra field on the spec to setforce
would do it? Not sure if that would mess with Flux and stop it reconciling. The expectation would be these updates are overwritten by Flux unless you have suspended the Kustomization.