When specifying two distinct tolerations with a common key in overrideRunnerSpec (e.g kubernetes.io/arch=amd64:noSchedule and kubernetes.io/arch=arm64:noSchedule), only the last toleration is kept by the merge operation during the concatenation of TerraformRepository and TerraformLayer OverrideRunnerSpec.
Easily reproductible by updating the related MergeTolerations test in common_test.go with two tolerations that share the same key
When specifying two distinct tolerations with a common key in overrideRunnerSpec (e.g
kubernetes.io/arch=amd64:noSchedule
andkubernetes.io/arch=arm64:noSchedule
), only the last toleration is kept by the merge operation during the concatenation of TerraformRepository and TerraformLayer OverrideRunnerSpec.Easily reproductible by updating the related MergeTolerations test in common_test.go with two tolerations that share the same key