Services DevOps DevSecOps Cloud Consulting Infrastructure Automation Managed Services AIOps MLOps DataOps Microservices 🔐 Private AINEW Solutions DevOps Transformation CI/CD Automation Platform Engineering Security Automation Zero Trust Security Compliance Automation Cloud Migration Kubernetes Migration Cloud Cost Optimisation AI-Powered Operations Data Platform Modernisation SRE & Observability Legacy Modernisation Managed IT Services 🔐 Private AI DeploymentNEW Products ✨ ZippyOPS AINEW 🛡️ ArmorPlane 🔒 DevSecOpsAsService 🖥️ LabAsService 🤝 Collab 🧪 SandboxAsService 🎬 DemoAsService Bootcamp 🔄 DevOps Bootcamp ☁️ Cloud Engineering 🔒 DevSecOps 🛡️ Cloud Security ⚙️ Infrastructure Automation 📡 SRE & Observability 🤖 AIOps & MLOps 🧠 AI Engineering 🎓 ZOLS — Free Learning Company About Us Projects Careers Get in Touch

Run MicroShift Kubernetes on Edge & IoT

Run MicroShift Kubernetes on Edge and IoT Devices

Managing Kubernetes clusters in resource-constrained environments, such as edge and IoT devices, can be challenging. Developers often face delays in deployment and governance, limiting the advantages of Kubernetes. Fortunately, MicroShift Kubernetes offers a lightweight solution, while platforms like Shipa simplify cluster management. In this guide, we’ll explore how to set up MicroShift and manage clusters efficiently using Shipa Cloud.

Moreover, ZippyOPS provides consulting, implementation, and managed services across DevOps, DevSecOps, DataOps, Cloud, Automated Ops, AIOps, MLOps, Microservices, Infrastructure, and Security. Their expertise ensures your Kubernetes clusters are optimized for both performance and governance (learn more).

MicroShift Kubernetes running on edge and IoT devices with Shipa Cloud integration

Why Choose MicroShift Kubernetes?

MicroShift Kubernetes is a lightweight, memory-optimized variant of OpenShift/Kubernetes, designed for environments with limited resources. Developed by Red Hat, it supports Fedora, RHEL, and CentOS distributions. At the same time, Shipa Cloud helps developers focus on building applications while reducing the operational overhead for platform operators. Integrating MicroShift with Shipa provides an efficient way to manage multiple clusters from a single interface.

According to Shipa documentation, MicroShift is not officially supported, but with the right setup, it can run seamlessly on Shipa Cloud. MicroShift uses the CRI-O lightweight container runtime, which ensures compatibility even in constrained environments.

Getting Started with MicroShift Kubernetes

1. Provision a MicroShift Cluster

You can set up a self-managed MicroShift cluster on any cloud VM (AWS, Azure, GCP) or a local machine. For this example, we’ll use Azure. Minimum requirements: 2 vCPU and 4 GB RAM.

Install Pulumi

Pulumi simplifies infrastructure provisioning with YAML and IaC. Install it with:

curl -fsSL https://get.pulumi.com | sh

Next, create a Pulumi account and generate an access token. This token allows programmatic access to projects and stacks, which can represent environments such as development, staging, or production.

Provision the VM

Using Pulumi YAML, define your Azure VM, network, and security group. Once configured, run:

pulumi up

Within minutes, your VM is ready.

2. Install MicroShift on CentOS

Once the VM is provisioned, install MicroShift using the official installation script:

curl -sfL https://raw.githubusercontent.com/nerdalert/microshift-installer/main/microshift-install.sh | sh -s -

The script installs CRI-O, MicroShift, and the OC CLI. It also sets up the kubeconfig file and ensures all pods are running.

3. Update kube-api Server Certificate

When connecting a self-managed MicroShift cluster to Shipa Cloud, you may encounter a certificate error:

Unable to connect to the server: x509: certificate

To resolve this, regenerate the kube-api certificate to include your VM’s public IP and DNS label using OpenSSL. After updating, your cluster can communicate securely with Shipa Cloud.

4. Connect MicroShift to Shipa Cloud

Provide the VM public IP to the Kubernetes control plane in the format: https://<IP>:6443. Then, execute the generated command on the cluster to deploy Shipa CRDs and related components.

Deploying an Nginx pod via Shipa Cloud may require patching the shipa-ingress-nginx service from LoadBalancer to NodePort to work on a self-managed VM:

oc patch svc shipa-ingress-nginx -n shipa -p '{"spec":{"type":"NodePort"}}'

After this change, your deployment should run successfully.

Benefits of Using MicroShift Kubernetes with Shipa

  • Efficiently manages multiple clusters from a single interface.
  • Reduces operational overhead for platform teams.
  • Optimized for low-resource environments without sacrificing functionality.
  • Seamless integration with CRI-O and Shipa Cloud.

Furthermore, ZippyOPS can support your organization in scaling and automating operations through consulting, implementation, and managed services. They specialize in Microservices, Cloud, MLOps, AIOps, Security, and Infrastructure, providing end-to-end solutions (solutions overview, products).

Conclusion

MicroShift Kubernetes makes it possible to deploy lightweight clusters on edge and IoT devices while Shipa Cloud simplifies cluster management. This approach reduces deployment time, enhances governance, and supports developers’ productivity. ZippyOPS can further streamline your operations with expert consulting, implementation, and managed services in DevOps, Cloud, Security, and more.

For demos and tutorials, explore their YouTube channel: ZippyOPS YouTube.

To discuss your next project or request services, contact ZippyOPS at sales@zippyops.com.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top