Feature Overview

Would like to put in a feature request for automation mesh isolation capabilities for customers/partners who will have mesh nodes into individual customer networks. The concern is that if a customer has access to the mesh node they could potentially obtain other customers hostname/ip address from the mesh by using receptorctl status command.

Background, and strategic fit

Imagine you have mesh nodes in various networks that should not know about each other or be able to be leveraged as an entry point into other said networks and need segregation/protection. I could see this being valuable for Kyndryl as well as other customer where they want to have network segmentation and isolation for security purposes.   

Assumptions

Assumption made the the network in which the mesh node is running, the end user would have capabilities to login and run receptorctl commands.