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
At present, Velero node-agent server searches the configMap with name hard coded node-agent-config for node agent configurations, i.e., affinities, concurrency, etc.
To make it more controllable and consistent, we want to apply below policies to the configMaps for Velero:
The configMap name must be specified to the velero/node-agent server parameters through installation
If the configMap name is specified but the configMap doesn't exist, it is ignored
If the configMap name is not specified, the configMap will not be used
Therefore, we need to make the node-agent configMap name configurable in the server parameters and we also need to change the document.
The text was updated successfully, but these errors were encountered:
At present, Velero node-agent server searches the configMap with name hard coded
node-agent-config
for node agent configurations, i.e., affinities, concurrency, etc.To make it more controllable and consistent, we want to apply below policies to the configMaps for Velero:
Therefore, we need to make the node-agent configMap name configurable in the server parameters and we also need to change the document.
The text was updated successfully, but these errors were encountered: