v2
What's New in ioFog 2?Core ConceptsArchitectureQuick Start With Local DeploymentQuick Start On Minikube and Vagrant
iofogctl - ioFog Unified Command Line InterfaceDownload And Install iofogctlGetting Familiar With iofogctliofogctl Resource ManagementConnecting To Existing Edge Compute NetworksLegacy Commands in iofogctl
IntroductionPrepare NetworkPrepare Remote HostsRemote - Deploy Control PlaneKubernetes - Prepare A ClusterKubernetes - Deploy Control Plane Using iofogctlKubernetes - Deploy Control Plane Using HelmSetup Agents
IntroductionAgent ConfigurationAttach / Detach an AgentVolume ManagementDocker Image Pruning
Writing MicroservicesioFog SDKDebugging
IntroductionGet To Know ioFogManage Our MicroservicesCreate Our First Microservice - JavaScriptDeploy Our Microservice
Distributed ApplicationsMicroservice Public PortsMove and Rename MicroservicesMicroservice Updates and LifecycleMicroservice Registry and Catalog ManagementMicroservice Logs
Kinds of ResourcesControl Plane YAML SpecificationAgent configuration YAML SpecificationApplication YAML SpecificationRoute YAML SpecificationCatalog Item YAML SpecificationRegistry YAML Specification
OverviewLegacy Controller CLI UsageController REST API Reference
OverviewLegacy Agent CLI UsageAgent Local API ReferenceAgent ConfigurationsRemote debugging using IntelliJ
System: Diagnostics MicroserviceSystem: Hardware Abstraction Layer MicroserviceSystem: Bluetooth REST API MicroserviceJSON REST API And Open Weather Map Microservices
Contributing GuidelinesCode of Conduct

Prepare your Kubernetes Cluster

Some components of an Edge Compute Network ('ECN') can be deployed on Kubernetes. These component include Controllers. iofogctl will also install ioFog Operator to assist in the Kubernetes deployed Control Plane. Resources for routing will also be deployed.

The ioFog platform can be installed easily on a managed Kubernetes Cluster provided by e.g. AWS, GCP, or Azure. Minikube is supported as well.

Using lightweight Kubernetes implementations such as MicroK8s or K3s are not fully supported. They will likely fail because those platforms do not assign host or IP addresses to Load Balancer services.

Kube Config

If we are familiar with kubectl, we will know that it relies on a configuration file typically found in ~/.kube/config which contains credentials for it to connect to the Kubernetes API Server.

iofogctl similarly relies on this configuration file. We need to make sure it is present on the host that we intend to use iofogctl from. The file can be saved anywhere on the host but it is recommended to keep it in ~/.kube/config because all of this guide's examples assume it to be there.

RBAC

In order for iofogctl or Helm to do its thing with our Kubernetes cluster, we will have to make sure we have the right RBAC permissions.

The way we add these permissions will depend on our respective Kubernetes provider. Ultimately, we need the User Account associated with our ~/.kube/config configuration file to have permission to use all verbs against the following resources:

  • roles
  • clusterroles
  • rolebindings
  • clusterrolebindings
  • services
  • deployments
  • statefulsets
  • pods
  • namespaces

If in doubt, we can use the default cluster role cluster-admin.

Using Google Kubernetes Engine

When using GKE to host our Kubernetes cluster, we need to ensure the gcloud CLI tool is installed. Once installed, we can connect to our cluster and get the requisite ~/.kube/config file by running:

gcloud container clusters get-credentials <NAME> --region <REGION>