Connectors are components of an ioFog Edge Compute Network ('ECN') which allow distributed Microservices to communicate amongst one another.
Like Controllers, there are two flavours of Connector deployments - Vanilla and Kubernetes. You are free to deploy Connectors onto the same Kubernetes cluster or remote host as your Controller. The latter approach is not recommended for production environments.
Create a template of connectors.yaml like so:
echo "---
apiVersion: iofog.org/v1
kind: Connector
metadata:
name: meerkat-1
spec:
kube:
config: ~/.kube/config" > /tmp/connector.yaml
To deploy, run:
iofogctl deploy -f /tmp/connector.yaml
Naturally, we can also use kubectl
to see what is happening on the Kubernetes cluster.
kubectl get pods
kubectl get services
The next section covers how to do the same thing we just did, but on a remote host instead of a Kubernetes cluster. We can skip ahead.
Create a template of connector.yaml like so:
echo "---
apiVersion: iofog.org/v1
kind: Connector
metadata:
name: meerkat-1
spec:
host: 38.101.23.3
ssh:
user: foo
keyFile: ~/.ssh/id_rsa" > /tmp/connector.yaml
Make sure to edit the host
, ssh.user
, and ssh.keyFile
fields to correspond with the remote host you are deploying to.
Once you have edited the fields to your liking, go ahead and run:
iofogctl deploy -f /tmp/connector.yaml
We can use the following commands to verify the Connector is up and running:
iofogctl get connectors
iofogctl describe connector meerkat-1