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"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThis page details the \u003ccode\u003eRestoreConfig.Types.NamespacedResourceRestoreMode\u003c/code\u003e enum from the Backup for GKE v1 API, defining how to handle existing namespaced resources during a restore operation.\u003c/p\u003e\n"],["\u003cp\u003eThe enum provides three modes: \u003ccode\u003eDeleteAndRestore\u003c/code\u003e, which deletes conflicting resources before restoring; \u003ccode\u003eFailOnConflict\u003c/code\u003e, which causes the restore to fail if conflicts are found; and \u003ccode\u003eUnspecified\u003c/code\u003e, which is an invalid state.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eDeleteAndRestore\u003c/code\u003e mode is intended for reverting a portion of a cluster to a previous state by deleting conflicting resources and all their references before restoring from the backup.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eFailOnConflict\u003c/code\u003e mode will stop the restore if a conflict occurs at the start of a restore or if it appears during the process, like from an out-of-band process creating resources.\u003c/p\u003e\n"],["\u003cp\u003eThis documentation covers versions of the API ranging from the latest 2.6.0 down to the beta version 1.0.0-beta01, providing information for each version.\u003c/p\u003e\n"]]],[],null,[]]
