provide --patch flag to allow users to perform patch behaviour,
and remove --force flag, this may break the backend compatibility,
able to be merged in minor or major version, issue: #8465.
Signed-off-by: Liu Ming <hit_oak_tree@126.com>
f.BoolVar(&client.DryRun,"dry-run",false,"simulate a rollback")
f.BoolVar(&client.Recreate,"recreate-pods",false,"performs pods restart for the resource if applicable")
f.BoolVar(&client.Force,"force",false,"force resource update through delete/recreate if needed")
f.BoolVar(&client.Patch,"patch",false,"make a patch to the current resource by the three way merge result if needed")
f.BoolVar(&client.DisableHooks,"no-hooks",false,"prevent hooks from running during rollback")
f.DurationVar(&client.Timeout,"timeout",300*time.Second,"time to wait for any individual Kubernetes operation (like Jobs for hooks)")
f.BoolVar(&client.Wait,"wait",false,"if set, will wait until all Pods, PVCs, Services, and minimum number of Pods of a Deployment, StatefulSet, or ReplicaSet are in a ready state before marking the release as successful. It will wait for as long as --timeout")