Its in the same repo, yes, but don't have to care about it, just as you may not care about Ci artifacts or editor config files, or gitignore files or whatever.

That info has to live somewhere, and in the same repo as the code doesn't sound that bad.

The value proposition of MRSK is to deploy servers on a few machines that you physically own.

Their focus is not on serverless-cloud-native-infinite-scaling.