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
There is a logic to check the existence of host_pods volume in node-agent pods when node-agent starts. If this volume is absent, node-agent pods will not start.
From 1.15, we have moved the data mover execution to dedicated pods, so data mover backup/restore don't rely on the host_pods volume. It is only required by fs-backup.
Therefore, we should not fail the node-agent pods if the host_pods volume is not there considering users may use node-agent for data mover backup/restore only.
The text was updated successfully, but these errors were encountered:
There is a logic to check the existence of
host_pods
volume in node-agent pods when node-agent starts. If this volume is absent, node-agent pods will not start.From 1.15, we have moved the data mover execution to dedicated pods, so data mover backup/restore don't rely on the
host_pods
volume. It is only required by fs-backup.Therefore, we should not fail the node-agent pods if the
host_pods
volume is not there considering users may use node-agent for data mover backup/restore only.The text was updated successfully, but these errors were encountered: