- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
",t};e.buildCustomizationMenuUi=t;function n(e){let t='
",t}function s(e){let n=e.filter.currentValue||e.filter.defaultValue,t='${e.filter.label}
`,e.filter.options.forEach(s=>{let o=s.id===n;t+=``}),t+="${e.filter.label}
`,t+=`ancestors
Type: UNORDERED_LIST_STRING
backup
Type: STRING
Provider name: backup
Description: Required. Immutable. A reference to the Backup used as the source from which this Restore will restore. Note that this Backup must be a sub-resource of the RestorePlan’s backup_plan. Format: projects/*/locations/*/backupPlans/*/backups/*
.
cluster
Type: STRING
Provider name: cluster
Description: Output only. The target cluster into which this Restore will restore data. Valid formats: - projects/*/locations/*/clusters/*
- projects/*/zones/*/clusters/*
Inherited from parent RestorePlan’s cluster value.
complete_time
Type: TIMESTAMP
Provider name: completeTime
Description: Output only. Timestamp of when the restore operation completed.
create_time
Type: TIMESTAMP
Provider name: createTime
Description: Output only. The timestamp when this Restore resource was created.
description
Type: STRING
Provider name: description
Description: Optional. User specified descriptive string for this Restore.
etag
Type: STRING
Provider name: etag
Description: Output only. etag
is used for optimistic concurrency control as a way to help prevent simultaneous updates of a restore from overwriting each other. It is strongly suggested that systems make use of the etag
in the read-modify-write cycle to perform restore updates in order to avoid race conditions: An etag
is returned in the response to GetRestore
, and systems are expected to put that etag in the request to UpdateRestore
or DeleteRestore
to ensure that their change will be applied to the same version of the resource.
filter
Type: STRUCT
Provider name: filter
Description: Optional. Immutable. Filters resources for Restore
. If not specified, the scope of the restore will remain the same as defined in the RestorePlan
. If this is specified and no resources are matched by the inclusion_filters
or everything is excluded by the exclusion_filters
, nothing will be restored. This filter can only be specified if the value of namespaced_resource_restore_mode is set to MERGE_SKIP_ON_CONFLICT
, MERGE_REPLACE_VOLUME_ON_CONFLICT
or MERGE_REPLACE_ON_CONFLICT
.
exclusion_filters
UNORDERED_LIST_STRUCT
exclusionFilters
ResourceSelector
of the exclusion_filters
.group_kind
STRUCT
groupKind
resource_group
STRING
resourceGroup
resource_kind
STRING
resourceKind
name
STRING
name
namespace
STRING
namespace
inclusion_filters
UNORDERED_LIST_STRUCT
inclusionFilters
inclusion_filters
will be selected for restoration. A resource will be selected if it matches any ResourceSelector
of the inclusion_filters
.group_kind
STRUCT
groupKind
resource_group
STRING
resourceGroup
resource_kind
STRING
resourceKind
name
STRING
name
namespace
STRING
namespace
labels
Type: UNORDERED_LIST_STRING
name
Type: STRING
Provider name: name
Description: Output only. The full name of the Restore resource. Format: projects/*/locations/*/restorePlans/*/restores/*
organization_id
Type: STRING
parent
Type: STRING
project_id
Type: STRING
project_number
Type: STRING
resource_name
Type: STRING
resources_excluded_count
Type: INT32
Provider name: resourcesExcludedCount
Description: Output only. Number of resources excluded during the restore execution.
resources_failed_count
Type: INT32
Provider name: resourcesFailedCount
Description: Output only. Number of resources that failed to be restored during the restore execution.
resources_restored_count
Type: INT32
Provider name: resourcesRestoredCount
Description: Output only. Number of resources restored during the restore execution.
restore_config
Type: STRUCT
Provider name: restoreConfig
Description: Output only. Configuration of the Restore. Inherited from parent RestorePlan’s restore_config.
all_namespaces
BOOLEAN
allNamespaces
cluster_resource_conflict_policy
STRING
clusterResourceConflictPolicy
CLUSTER_RESOURCE_CONFLICT_POLICY_UNSPECIFIED
- Unspecified. Only allowed if no cluster-scoped resources will be restored.USE_EXISTING_VERSION
- Do not attempt to restore the conflicting resource.USE_BACKUP_VERSION
- 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.cluster_resource_restore_scope
STRUCT
clusterResourceRestoreScope
all_group_kinds
BOOLEAN
allGroupKinds
excluded_group_kinds
UNORDERED_LIST_STRUCT
excludedGroupKinds
resource_group
STRING
resourceGroup
resource_kind
STRING
resourceKind
no_group_kinds
BOOLEAN
noGroupKinds
selected_group_kinds
UNORDERED_LIST_STRUCT
selectedGroupKinds
resource_group
STRING
resourceGroup
resource_kind
STRING
resourceKind
excluded_namespaces
STRUCT
excludedNamespaces
namespaces
UNORDERED_LIST_STRING
namespaces
namespaced_resource_restore_mode
STRING
namespacedResourceRestoreMode
NAMESPACED_RESOURCE_RESTORE_MODE_UNSPECIFIED
- Unspecified (invalid).DELETE_AND_RESTORE
- 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.FAIL_ON_CONFLICT
- 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.MERGE_SKIP_ON_CONFLICT
- This mode merges the backup and the target cluster and skips the conflicting resources. If a single resource to restore exists in the cluster before restoration, the resource will be skipped, otherwise it will be restored.MERGE_REPLACE_VOLUME_ON_CONFLICT
- This mode merges the backup and the target cluster and skips the conflicting resources except volume data. If a PVC to restore already exists, this mode will restore/reconnect the volume without overwriting the PVC. It is similar to MERGE_SKIP_ON_CONFLICT except that it will apply the volume data policy for the conflicting PVCs: - RESTORE_VOLUME_DATA_FROM_BACKUP: restore data only and respect the reclaim policy of the original PV; - REUSE_VOLUME_HANDLE_FROM_BACKUP: reconnect and respect the reclaim policy of the original PV; - NO_VOLUME_DATA_RESTORATION: new provision and respect the reclaim policy of the original PV. Note that this mode could cause data loss as the original PV can be retained or deleted depending on its reclaim policy.MERGE_REPLACE_ON_CONFLICT
- This mode merges the backup and the target cluster and replaces the conflicting resources with the ones in the backup. If a single resource to restore exists in the cluster before restoration, the resource will be replaced with the one from the backup. To replace an existing resource, the first attempt is to update the resource to match the one from the backup; if the update fails, the second attempt is to delete the resource and restore it from the backup. Note that this mode could cause data loss as it replaces the existing resources in the target cluster, and the original PV can be retained or deleted depending on its reclaim policy.no_namespaces
BOOLEAN
noNamespaces
restore_order
STRUCT
restoreOrder
group_kind_dependencies
UNORDERED_LIST_STRUCT
groupKindDependencies
requiring
STRUCT
requiring
resource_group
STRING
resourceGroup
resource_kind
STRING
resourceKind
satisfying
STRUCT
satisfying
resource_group
STRING
resourceGroup
resource_kind
STRING
resourceKind
selected_applications
STRUCT
selectedApplications
namespaced_names
UNORDERED_LIST_STRUCT
namespacedNames
name
STRING
name
namespace
STRING
namespace
selected_namespaces
STRUCT
selectedNamespaces
namespaces
UNORDERED_LIST_STRING
namespaces
substitution_rules
UNORDERED_LIST_STRUCT
substitutionRules
new_value
STRING
newValue
original_value_pattern
STRING
originalValuePattern
target_group_kinds
UNORDERED_LIST_STRUCT
targetGroupKinds
resource_group
STRING
resourceGroup
resource_kind
STRING
resourceKind
target_json_path
STRING
targetJsonPath
target_namespaces
UNORDERED_LIST_STRING
targetNamespaces
transformation_rules
UNORDERED_LIST_STRUCT
transformationRules
description
STRING
description
field_actions
UNORDERED_LIST_STRUCT
fieldActions
from_path
STRING
fromPath
op
STRING
op
OP_UNSPECIFIED
- Unspecified operationREMOVE
- The ‘remove’ operation removes the value at the target location.MOVE
- The ‘move’ operation removes the value at a specified location and adds it to the target location.COPY
- The ‘copy’ operation copies the value at a specified location to the target location.ADD
- The ‘add’ operation performs one of the following functions, depending upon what the target location references: 1. If the target location specifies an array index, a new value is inserted into the array at the specified index. 2. If the target location specifies an object member that does not already exist, a new member is added to the object. 3. If the target location specifies an object member that does exist, that member's value is replaced.TEST
- The ’test’ operation tests that a value at the target location is equal to a specified value.REPLACE
- The ‘replace’ operation replaces the value at the target location with a new value. The operation object MUST contain a ‘value’ member whose content specifies the replacement value.path
STRING
path
value
STRING
value
resource_filter
STRUCT
resourceFilter
group_kinds
UNORDERED_LIST_STRUCT
groupKinds
resource_group
STRING
resourceGroup
resource_kind
STRING
resourceKind
json_path
STRING
jsonPath
namespaces
UNORDERED_LIST_STRING
namespaces
volume_data_restore_policy
STRING
volumeDataRestorePolicy
VOLUME_DATA_RESTORE_POLICY_UNSPECIFIED
- Unspecified (illegal).RESTORE_VOLUME_DATA_FROM_BACKUP
- For each PVC to be restored, create a new underlying volume and PV from the corresponding VolumeBackup contained within the Backup.REUSE_VOLUME_HANDLE_FROM_BACKUP
- For each PVC to be restored, attempt to reuse the original PV contained in the Backup (with its original underlying volume). This option is likely only usable when restoring a workload to its original cluster.NO_VOLUME_DATA_RESTORATION
- For each PVC to be restored, create PVC without any particular action to restore data. In this case, the normal Kubernetes provisioning logic would kick in, and this would likely result in either dynamically provisioning blank PVs or binding to statically provisioned PVs.volume_data_restore_policy_bindings
UNORDERED_LIST_STRUCT
volumeDataRestorePolicyBindings
policy
STRING
policy
VOLUME_DATA_RESTORE_POLICY_UNSPECIFIED
- Unspecified (illegal).RESTORE_VOLUME_DATA_FROM_BACKUP
- For each PVC to be restored, create a new underlying volume and PV from the corresponding VolumeBackup contained within the Backup.REUSE_VOLUME_HANDLE_FROM_BACKUP
- For each PVC to be restored, attempt to reuse the original PV contained in the Backup (with its original underlying volume). This option is likely only usable when restoring a workload to its original cluster.NO_VOLUME_DATA_RESTORATION
- For each PVC to be restored, create PVC without any particular action to restore data. In this case, the normal Kubernetes provisioning logic would kick in, and this would likely result in either dynamically provisioning blank PVs or binding to statically provisioned PVs.volume_type
STRING
volumeType
VOLUME_TYPE_UNSPECIFIED
- DefaultGCE_PERSISTENT_DISK
- Compute Engine Persistent Disk volumestate
Type: STRING
Provider name: state
Description: Output only. The current state of the Restore.
Possible values:
STATE_UNSPECIFIED
- The Restore resource is in the process of being created.CREATING
- The Restore resource has been created and the associated RestoreJob Kubernetes resource has been injected into target cluster.IN_PROGRESS
- The gkebackup agent in the cluster has begun executing the restore operation.SUCCEEDED
- The restore operation has completed successfully. Restored workloads may not yet be operational.FAILED
- The restore operation has failed.DELETING
- This Restore resource is in the process of being deleted.VALIDATING
- The Kubernetes resources created by this Restore are being validated.state_reason
Type: STRING
Provider name: stateReason
Description: Output only. Human-readable description of why the Restore is in its current state. This field is only meant for human readability and should not be used programmatically as this field is not guaranteed to be consistent.
tags
Type: UNORDERED_LIST_STRING
uid
Type: STRING
Provider name: uid
Description: Output only. Server generated global unique identifier of UUID format.
update_time
Type: TIMESTAMP
Provider name: updateTime
Description: Output only. The timestamp when this Restore resource was last updated.
volume_data_restore_policy_overrides
Type: UNORDERED_LIST_STRUCT
Provider name: volumeDataRestorePolicyOverrides
Description: Optional. Immutable. Overrides the volume data restore policies selected in the Restore Config for override-scoped resources.
policy
STRING
policy
VOLUME_DATA_RESTORE_POLICY_UNSPECIFIED
- Unspecified (illegal).RESTORE_VOLUME_DATA_FROM_BACKUP
- For each PVC to be restored, create a new underlying volume and PV from the corresponding VolumeBackup contained within the Backup.REUSE_VOLUME_HANDLE_FROM_BACKUP
- For each PVC to be restored, attempt to reuse the original PV contained in the Backup (with its original underlying volume). This option is likely only usable when restoring a workload to its original cluster.NO_VOLUME_DATA_RESTORATION
- For each PVC to be restored, create PVC without any particular action to restore data. In this case, the normal Kubernetes provisioning logic would kick in, and this would likely result in either dynamically provisioning blank PVs or binding to statically provisioned PVs.selected_pvcs
STRUCT
selectedPvcs
namespaced_names
UNORDERED_LIST_STRUCT
namespacedNames
name
STRING
name
namespace
STRING
namespace
volumes_restored_count
Type: INT32
Provider name: volumesRestoredCount
Description: Output only. Number of volumes restored during the restore execution.