Configuring Namespace Access and Memory Limit
The Replicated admin console requires access to the namespace where Velero is installed. If your admin console is running with minimal role-based-access-control (RBAC) privileges, you must enable the admin console to access Velero.
Additionally, if the application uses a large amount of memory, you can configure the default memory limit to help ensure that Velero runs successfully with snapshots.
Configure Namespace Access
This procedure applies only to existing cluster installations (online and air gap) where the admin console is running with minimal role-based-access-control (RBAC) privileges.
Run the following command to enable the admin console to access the Velero namespace:
kubectl kots velero ensure-permissions --namespace ADMIN_CONSOLE_NAMESPACE --velero-namespace VELERO_NAMESPACE
ADMIN_CONSOLE_NAMESPACEwith the namespace on the cluster where the admin console is running.
VELERO_NAMESPACEwith the namespace on the cluster where Velero is installed.
Increase the Memory Limit
This procedure applies to all online and air gap installations.
You can increase the default memory limit for the node-agent (restic) Pod if your application is particularly large. Velero sets default limits for the velero Pod and the node-agent (restic) Pod during installation. There is a known issue with restic that causes high memory usage, which can result in failures during backup creation when the Pod reaches the memory limit. For more information about configuring Velero resource requests and limits, see Customize resource requests and limits in the Velero documentation.
Alternatively, you can potentially avoid the node-agent (restic) Pod reaching the memory limit during backup creation by running the following kubectl command to lower the memory garbage collection target percentage on the node-agent (restic) daemon set:
Velero v1.10 and later:
kubectl -n velero set env daemonset/node-agent GOGC=1
Velero versions earlier than v1.10:
kubectl -n velero set env daemonset/restic GOGC=1