Description

Setting globalResources does not result in any change. Root cause is usage of unknown environment variables:
BACKUP_GLOBALCPU_REQUEST
BACKUP_GLOBALMEMORY_REQUEST
BACKUP_GLOBALCPU_LIMIT
BACKUP_GLOBALMEMORY_LIMIT

The actual environment variables are (note the added underscore)
BACKUP_GLOBAL_CPU_REQUEST
BACKUP_GLOBAL_MEMORY_REQUEST
BACKUP_GLOBAL_CPU_LIMIT
BACKUP_GLOBAL_MEMORY_LIMIT

A workaround is to set these directly through envVars.

Additional Context

No response

Logs

Expected Behavior

setting globalResources should result in setting the correct environment variables.

Steps To Reproduce

create a helm deployment with globalResources set

observe that the (wrong) environment variables are set on the k8up deployment.

Version of K8up

v4.8.4

Version of Kubernetes

any

Distribution of Kubernetes

any