zephyr
microk8s
Our great sponsors
zephyr | microk8s | |
---|---|---|
57 | 65 | |
9,402 | 8,055 | |
3.4% | 1.5% | |
10.0 | 8.5 | |
3 days ago | 15 days ago | |
C | Python | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
zephyr
-
VisionFive 2 ROM addresses for Zephyr RTOS
I am working on adding support for VisionFive 2 in Zephyr RTOS. I have created a device tree by referencing the starfive linux, patches of hifive_unmatched FU740 SoC and patches of BeagleV Starlight.
-
Adding support for visionfive2 in zephyr rtos
We are unsure on how to proceed further with this error. We have opened a github discussion regarding the same issue.
-
Learning to write device drivers using C/C++ in Zephyr OS
Then there are samples. Look through it for anything useful. RC522 uses SPI, so getting that to work would be a good first step.
-
PlatformIO and Zephyr is a bad idea
In this thread u/ikravets explained that there hasn't been much demand for Zephyr, which is why they aren't doing anything with it, and in this pull request Zephyr decided to no longer recommend PlatformIO in their documentation.
-
Libraries for Zephyr (Nordic SDK 2.3)
I'd start out with another IMU example like this one: https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/sensor/lsm6dso
This is exactly the library you're looking for. You just need to create an application and instantiate it. The samples for other drivers can show you how to do that. https://github.com/zephyrproject-rtos/zephyr/tree/main/drivers/sensor/ism330dhcx
- Examples of excellently-written projects.
-
Sensor FIFO interrupt implementation in Zephyr
2) There's nothing better I guess. Just look through the samples and try to understand what they're doing. In the MAX30101 example they only enabled the sensor itself. So the configuration was already done in the .dts file. If you look into that file, you'll see how exactly it was configured. I'd urge you to go through the samples/sensor directory and look at as many overlay files as possible to see how they can be configured.
The Zephyr driver for MAX30101 does not have much functionality, it lacks sensor triggering support for example https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/sensor/max30101/max30101.c so you need to implement it yourself, maybe you could contribute to the driver itself.
-
Git archive generation meets Hyrum's law
I think that's uncharitable. Almost no one realized these things were being generated. We all assumed that links to github's "releases" were just links to files because they look like links to files! Here's one to Zephyr 3.2.0: https://github.com/zephyrproject-rtos/zephyr/archive/refs/ta...
You pull that and get a tarball that is presented to the world as an "official release". Looks like a file. Acts like a file. It's a file.
So now your package manager or reproducible build engine or whatever needs a reference to the "official source code release", and what do you point it to? That file, obviously. It's right there on the "release" page for the download. And of course you checksum it for security, because duh.
Then last week all of a sudden that file changed! Sure, it has the same contents. But the checksum that you computed in good faith based on the official release tarball doesn't match!
If there's a misunderstanding here, it's on github and not the users. They can't be providing official release tarballs if they won't guarantee consistency. "As documented", this feature was a huge footgun. That's bad.
microk8s
-
Deploying a Web Service on a Cloud VPS Using Kubernetes MicroK8s: A Comprehensive Guide
And install microk8s:
-
Seeking Guidance for Transitioning to Kubernetes and SRE/DevOps for traditional infrastructure team
One quick and easy win I can recommend, is microk8s.
-
Cuber: Deploy your apps on Kubernetes easily
microk8s currently has a showstopping issue that makes it guaranteed to have an irrecoverable failure in HA mode. see https://github.com/canonical/microk8s/issues/3227
k0s is better but also has a lot of bugs. it's the closest to vanilla kubernetes among all the distributions.
> like the simplest GPU support
linux users should be ready to install the nvidia device plugin. if they can't do that, they're never going to succeed in running a gpu accelerated application on their cluster anyway.
> like bootstrapping
in my experience, writing all the bootstrap scripts is painful. but now that there's chatgpt, so much of the drudgery as gone away.
-
I turn my company’s PC into my own “Vercel-like” platform
MicroK8S to spin up a Kubernetes cluster
-
Set up docker and kubernetes in ubuntu 22.04
We will be using docker and microk8s from Canonical. For running our software during development, we will be using skaffold which is a great tool developed by Google.
- What's the most sane way to operate a K8s cluster?
-
How’s everyone running k8s on their homelab’s
I'm curious about this myself. Right now I'm considering putting microk8s on my Ubuntu server.
-
About to start my Homelab
microk8s cluster, fully working Kubernetes in under 5 minutes
- Despliega un clúster de Kubernetes en segundos con k3sup
-
CEL for admission controller with ValidatingAdmissionPolicy in K8s 1.26
microk8s - https://microk8s.io
What are some alternatives?
rancher - Complete container management platform
FreeRTOS-Kernel - FreeRTOS kernel files only, submoduled into https://github.com/FreeRTOS/FreeRTOS and various other repos.
k3s - Lightweight Kubernetes
mbed-os - Arm Mbed OS is a platform operating system designed for the internet of things
RIOT - RIOT - The friendly OS for IoT
nuttx - Apache NuttX is a mature, real-time embedded operating system (RTOS)
docker - Moby Project - a collaborative project for the container ecosystem to assemble container-based systems [Moved to: https://github.com/moby/moby]
k3d - Little helper to run CNCF's k3s in Docker
wasm-micro-runtime - WebAssembly Micro Runtime (WAMR)
mongoose-os - Mongoose OS - an IoT Firmware Development Framework. Supported microcontrollers: ESP32, ESP8266, CC3220, CC3200, STM32F4, STM32L4, STM32F7. Amazon AWS IoT, Microsoft Azure, Google IoT Core integrated. Code in C or JavaScript.
k0s - k0s - The Zero Friction Kubernetes
microshift - A small form factor OpenShift/Kubernetes optimized for edge computing