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
{{ message }}
This repository was archived by the owner on Feb 29, 2024. It is now read-only.
I think it is important that the slurm config file is evaluated not only when changes are made but also right at the first start of goRTR.
a possible use case would be to run several goRTR instances in kubernetes clusters, check the locallyAddedAssertions via rtrdump and use them to control the readinessProbe.
Of course an evaluation after changing the slurm file content as proposed here could be useful as well.
I think it is important that the slurm config file is evaluated not only when changes are made but also right at the first start of goRTR.
a possible use case would be to run several goRTR instances in kubernetes clusters, check the locallyAddedAssertions via rtrdump and use them to control the readinessProbe.
Of course an evaluation after changing the slurm file content as proposed here could be useful as well.