Closed aws-patrickc closed 1 month ago
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stalled for 5 days with no activity.
Can this be reopened?
Is there a reason that resolveConflicts
is supported as an option in a config file but not from the CLI?
@out-of-band
There's a --force
flag which essentially implements --resolve-conflicts Overwrite
, and the default is None
. There's indeed no way of configuring --resolve-conflicts Preserve
via CLI flags. The --force
flag would ideally be deprecated.
By the time we implemented the resolveConflicts
option, we also decided that the general direction for eksctl should be more config file centric. Hence why the option does not exist in the CLI.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stalled for 5 days with no activity.
What feature/behavior/change do you want?
Currently eksctl update addon command does not include the "--resolve-conflicts" flag as can be seen on v0.153.0 or later:
Ideally we should be able to run something like:
Why do you want this feature?
"eksctl" is used extensively to manage EKS clusters and add-ons, it would be great to have the ability to update the add-on with using eksctl command to preserve or overwrite any conflict as per the AWS CLI