You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/backup/azure-kubernetes-service-backup-overview.md
+65-66Lines changed: 65 additions & 66 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ ms.topic: conceptual
5
5
ms.service: backup
6
6
ms.custom:
7
7
- ignite-2023
8
-
ms.date: 11/14/2023
8
+
ms.date: 11/30/2023
9
9
author: AbhishekMallick-MS
10
10
ms.author: v-abhmallick
11
11
---
@@ -69,9 +69,6 @@ You can now use the Custom Hooks capability available in Azure Backup for AKS.
69
69
70
70
Azure Backup for AKS enables you to execute Custom Hooks as part of the backup and restore operation. Hooks are commands configured to run one or more commands to execute in a pod under a container during the backup operation or after restore. They allow you to define these hooks as a custom resource and deploy in the AKS cluster to be backed up or restored. Once the custom resource is deployed in the AKS cluster in the required Namespace, you need to provide the details as input for the Configure Backup/Restore flow, and the Backup extension runs the hooks as defined in the YAML file.
71
71
72
-
>[!Note]
73
-
>Hooks aren't executed in a *shell* on the containers.
74
-
75
72
There are two types of hooks:
76
73
77
74
### Backup Hooks
@@ -88,43 +85,45 @@ metadata:
88
85
name: bkphookname0
89
86
namespace: default
90
87
spec:
91
-
# BackupHook Name. This is the name of the hook that will be executed during backup.
92
-
# compulsory
93
-
name: hook1
94
-
# Namespaces where this hook will be executed.
95
-
includedNamespaces:
96
-
- hrweb
97
-
excludedNamespaces:
98
-
labelSelector:
99
-
# PreHooks is a list of BackupResourceHooks to execute prior to backing up an item.
100
-
preHooks:
101
-
- exec:
102
-
# Container is the container in the pod where the command should be executed.
103
-
container: webcontainer
104
-
# Command is the command and arguments to execute.
105
-
command:
106
-
- /bin/uname
107
-
- -a
108
-
# OnError specifies how Velero should behave if it encounters an error executing this hook
109
-
onError: Continue
110
-
# Timeout is the amount of time to wait for the hook to complete before considering it failed.
0 commit comments