Edge Conductor¶
Edge Conductor is a framework to create, manage, and operate Kubernetes clusters for IoT workloads. It provides a number of services and features for IoT today, with more under development.
Edge Conductor can be used to deploy Kubernetes clusters in several different ways. The deployment methods rely on a “Day-0” host to run the Edge Conductor tools that download, build, and provision the required software. All deployment methods also rely on a management console to operate and administer the cluster:
Virtual cluster: All nodes in the cluster are virtualized as container images and Kubernetes is deployed on your local machine. The Day-0 host and management console are also the user’s local machine. This deployment model is implemented using “KIND”.
On-premise cluster: All nodes in the cluster are actual physical (or virtual) machines. The Day-0 and management console functions are performed on machines outside the cluster. This deployment model is implemented using either Rancher RKE or the Cluster API.
Existing cluster: All nodes in the cluster have already been provisioned and are running Kubernetes, for example as in a StarlingX, VMWare Tanzu, or OpenShift cluster or similar Kubernetes deployment. In this model, only services are deployed and managed by the Edge Conductor tools. The Day-0 machine and management cluster are assumed to already exist.
Please refer to the Edge Conductor documentation in the Edge Conductor release EdgeConductor-x.x.x.tar.gz located at Support/Edge-Conductor within the ECI release archive (release-eci_#.#.zip) for more information on installing, configuring, and deploying Edge Conductor:
└── Support └── Edge-Conductor └── EdgeConductor-x.x.x.tar.gz