When conflicting top-level resources (either Namespaces or
ProtectedApplications, depending upon the scope) are encountered, this
will first trigger a delete of the conflicting resource AND ALL OF ITS
REFERENCED RESOURCES (e.g., all resources in the Namespace or all
resources referenced by the ProtectedApplication) before restoring the
resources from the Backup. This mode should only be used when you are
intending to revert some portion of a cluster to an earlier state.
FailOnConflict
If conflicting top-level resources (either Namespaces or
ProtectedApplications, depending upon the scope) are encountered at the
beginning of a restore process, the Restore will fail. If a conflict
occurs during the restore process itself (e.g., because an out of band
process creates conflicting resources), a conflict will be reported.
[[["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 content describes the `RestoreConfig.Types.NamespacedResourceRestoreMode` enum within the Backup for GKE v1 API, detailing how it manages existing namespaced resources during a restore operation."],["The API provides three modes for handling conflicts with existing resources: `DeleteAndRestore`, which deletes conflicting resources before restoring; `FailOnConflict`, which halts the restore if conflicts are found; and `Unspecified`, which is an invalid state."],["Version history for the `NamespacedResourceRestoreMode` documentation is available, ranging from the latest version 2.6.0 down to the 1.0.0-beta01 release."],["The `DeleteAndRestore` mode deletes all referenced resources along with the conflicting top-level resources before restoring, which is recommended only when reverting a cluster to a previous state."]]],[]]
