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 has been 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.
The text was updated successfully, but these errors were encountered:
I saw the merge request in the stayrtr project and tried to get this app to run a few days ago, but it somehow failed. I can't remember what exactly the problem was, but i can try to reproduce it again. Since i'm not a Go expert, i don't know how they handle it.
Maybe I should give it a try and go for stayrtr since it seems goRTR is no longer maintained?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: