Engine
- Retired ioFog Connector in favor of new Red Hat Skupper routers based on Apache AMQP
- Expand supported architectures from x86/ARM to any number of defined architectures and architecture + capability labels
- Finalize definition of agent-to-controller interface and APIs to enable the community to write their own ioFog Agents in any language
- Docker pruning in Agent
- Registry management in Controller
- Universal logging capability with centralized access and distributed handling
iofogctl
- Enhanced status information about edge microservices
- Agent attach/detach functionality
- Microservice move functionality
- Support for Windows OS
Kubernetes
- Better Minikube and local environment experience (show how this complements with the platform repo / tools)
Integrations
- Eclipse Hono integration for starting up a Hono environment with edge capabilities from ioFog - key Hono components deployed and managed at the edge
- VMware Tanzu integration for providing seamless edge capabilities for managed k8s environments
YAML specification for iofogctl commands have changed to incorporate the new Router model. Please see documentation for ioFog release 2.0 on iofog.org website.
Compatible platforms and architectures for all relevant ioFog components:
- Agent & Router
- x86, arm, arm64
- Debian, Ubuntu, Fedora, CentOS, RHEL
- Controller
- x86, arm, arm64
- Debian, Ubuntu, Fedora, CentOS, RHEL + any system that runs NodeJS
- Kubelet
- x86-64
- Docker image to run on Kuberentes
- Operator
- x86-64
- Docker image to run on Kuberentes
- iofogctl
- x86-64
- Debian, Ubuntu, Fedora, CentOS, RHEL, MacOS, Windows + any system that runs Go