Sorry, it works.
sounds good, happy to hear that.
we have never done using Navigation2 with Kubernetes so this is really good information. thanks.
what would you say to making each robot as a single-node cluster (as opposed to worker node) and build a multi-cluster system for multi-robots?
i would say probable and possible, using federation to connect each cluster. actually we have tried to use federation to connect multi-cluster system, it works okay. but our use case is more like generic multi-cluster system like cloud and edge. not have concrete image or use case for what you mention.
Kubernetes is designed to orchestrate containers not nodes,
i guess this is correct. but it does not mean the following,
‘nodeSelector’ is simply a guideline to K8s, not a rule that K8s should follow.
sounds politics for me,
at least k8s has interface for Pods assignment for Nodes such as label, nodeSelector and nodeAffinity. besides, there is Device-Plugins to advertise hardware device on the specific nodes.