K3s Lightweight Kubernetes vs. Microsoft Azure IoT Edge

K3s Lightweight Kubernetes is well suited for local development. K3s Lightweight Kubernetes is not well suited when you need backward support. In the case that you want to test an application that is still using deprecated APIs or CRDs which are supported on popular managed Cloud Kubernetes Distributions, because K3s Lightweight Kubernetes is trying to be a lightweight application and dropping early support for APIs/CRDs marked for deprication K3s Lightweight Kubernetes will not be a good solution. If you are trying to test Kubernetes etc, functionality, K3s Lightweight Kubernetes is not a good case since it's using Dqlite or SQLite.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

Deployment of mission critical business support solutions particularly those that support virtual learning and video conferencing environments. This is because they help organisations such as the university to effectively transition to a digitally compliant organisation.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• Virtual clusters
• IoT devices
• Local development
• Raspberry Pi

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• It works even if there is no internet at client location. It will record all the generated data and only send them to cloud storage when there is internet connection.
• It allows you to bring cloud functionality down to Edge location in the form of docker container.
• It also supports two way communication from device to cloud and vice-versa.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• Option to deploy a self managed k3s in the cloud
• Support to deploy it with kubeadm
• Integration with prometheus & grafana

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• For some reason, the containerized architecture was also making this very hard
• Had some issues when debugging edge modules, needs a professional grade remote debugging
• Industrial automation still requires attention. OPC-UA was good but Modbus or custom PLCs etc was painful to set up

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

Most of the time it works perfectly, does not require any attention, but when there is a problem, it's really hard to diagnose it. I think the documentation for the positive scenarios are good on the Microsoft side, but for negative scenarios, I don't think there is enough community help out there, in my opinion.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

We have mostly used kind, minikube, and Docker Desktop Kubernetes for local development. Only kind has lower resource requirements, but K3s Lightweight Kubernetes seems to be even lighter. It is a big benefit to be able to deploy a K3s Lightweight Kubernetes cluster in seconds locally in our workstation, there is no cost, and it makes it easy to redeploy from scratch no matter how many times we want. The removal of deprecated APIs or CRDs also makes it more secure since it reduces unnecessarily exposed attack vectors.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

The reason Behind this is the cost, as Microsoft provides solutions and integrations of services cheaper than AWS.

• Engineers have been able to run more microservices locally with K3s Lightweight Kubernetes instead of Minikube, which is more resources hungry

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• Very valuable return on investment for IT capex committed to the deployment
• Improvements in overall organisational efficiency and agility
• Repositioning the organisation to become digitally transformed

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info