Idempotency-Key header vs. etag/resourceVersion deduplication for Rancher API retries
Goal: configure Rancher API call retries so that transient failures do not cause duplicate resource creation or updates. Constraints: the Idempotency-Key header is only honored in Rancher v2.6+ when the feature flag is enabled; older versions ignore it and may duplicate writes. Relying on etag/resourceVersion for deduplication assumes the underlying Kubernet