Prepare Network
Once we have a set of remote hosts (and/or a Kubernetes cluster) we need to make sure that we have appropriate firewall rules for the ioFog components that we will start deploying on those remote hosts.
The following is an exhaustive list of the ingress firewall rules required for any ioFog Edge Compute Network.
| Component | Protocol/Port | Description |
|---|---|---|
| Controller | tcp:51121 | Controller API to be accessible from Agents and potctl. |
| Controller | http:8008 | ECN Viewer to be accessible by ECN admins or users. |
| potctl | tcp:22 | SSH access to install ioFog Controller and Agent on remote hosts. |
Please keep in mind that once we start exposing microservices using public ports in our ECNs, there will be additional ports that we expect to be accessible from outside of the network.
Where to go from here?
Regardless of the type of deployment we need, next we have to prepare remote hosts for Controller and Agents (in case of remote deployment), or just for Agents (in case of Kubernetes deployment).
See anything wrong with the document? Help us improve it!