Unspecified. Only allowed if no cluster-scoped resources will be
restored.
UseBackupVersion
Delete the existing version before re-creating it from the Backup.
This is a dangerous option which could cause unintentional
data loss if used inappropriately. For example, deleting a CRD will
cause Kubernetes to delete all CRs of that type.
UseExistingVersion
Do not attempt to restore the conflicting resource.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-21 UTC."],[[["The document provides reference information for the `RestoreConfig.Types.ClusterResourceConflictPolicy` enum within the Google Cloud GKE Backup v1 API."],["This enum defines how the API should handle conflicts when cluster-scoped resources being restored already exist in the target cluster."],["There are three possible values for this policy: `Unspecified`, `UseBackupVersion` (delete the existing resource and replace it), and `UseExistingVersion` (do not restore the conflicting resource)."],["The latest version of the documentation available is 2.6.0, and older versions from 2.5.0 to 2.0.0, along with 1.0.0-beta01 are also available."]]],[]]