-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
task
follow-up 3
#412
Comments
I'd advise against. |
Given the availability and performance1 requirements of the use cases this tool covers (i.e. experimentation and not serving), the current behavior seems appropriate: specifying a region causes the Footnotes
|
Definitely. Kubernetes syntax is too rich for a single string variable; trying to fit everything into a single parameter can be detrimental. |
Agreed for affinity & selectors, not quite for regions and zones. |
Latency between client machine and the hosted compute resources. None of this translates nicely to k8s node selection - it CAN, if you set up your node groups or use labels in a very specific way, such that you actually pick nodes in specific cloud zone, maybe cross-node-groups, but that's besides the point. Anything that has to do with selecting nodes on k8s is only meaningful in the context of how that specific cluster and its node groups are set up. |
minor nitpicks from #258 (comment):
p2-nice-to-have
rclone
connection strings properly Connection strings for on the fly backend configuration rclone/rclone#4996 (comment)The text was updated successfully, but these errors were encountered: