node-feature-discovery
cri-tools
Our great sponsors
node-feature-discovery | cri-tools | |
---|---|---|
8 | 7 | |
675 | 1,542 | |
3.3% | 2.2% | |
9.5 | 9.2 | |
6 days ago | 1 day ago | |
Go | Go | |
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.
node-feature-discovery
-
Those running Kubernetes, what is in your core stack? And what "gem" can you not live without?
node-feature-discovery and descheduler
-
How can Intel quick sync be exposed to a pod?
Take a look at the NFD repo, they have instructions for deploying without helm β https://github.com/kubernetes-sigs/node-feature-discovery
This one https://github.com/kubernetes-sigs/node-feature-discovery is an official method of node discovery that puts certain labels on nodes, but I can't see the label "feature.node.kubernetes.io/custom-intel-gpu" being created. Am I missing where that label comes from? Is that where the helm version comes in from https://github.com/billimek/k8s-gitops/blob/master/kube-system/node-feature-discovery/node-feature-discovery.yaml does this one apply that label named?
When deploying without the helm chart, you need to define that in the ConfigMap. Looks like itβs here: https://github.com/kubernetes-sigs/node-feature-discovery/blob/master/nfd-daemonset-combined.yaml.template#L137-L229
cri-tools
-
Migrating from dockershim to containerd
Installing crictl (https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/crictl.md) was helpful, as well as journalctl -u containerd.
- kubectl get nodes -o wide shows containerd runtime, but sudo ctr containers list doesn't return any containers on host
-
k8s-the-hard-way
# wget https://github.com/kubernetes-sigs/cri-tools/releases/download/v1.21.0/crictl-v1.21.0-linux-amd64.tar.gz \ https://github.com/opencontainers/runc/releases/download/v1.0.0-rc93/runc.amd64 \ https://github.com/containernetworking/plugins/releases/download/v0.9.1/cni-plugins-linux-amd64-v0.9.1.tgz \ https://github.com/containerd/containerd/releases/download/v1.4.4/containerd-1.4.4-linux-amd64.tar.gz \ https://storage.googleapis.com/kubernetes-release/release/v1.21.0/bin/linux/amd64/kubectl \ https://storage.googleapis.com/kubernetes-release/release/v1.21.0/bin/linux/amd64/kube-proxy \ https://storage.googleapis.com/kubernetes-release/release/v1.21.0/bin/linux/amd64/kubelet
-
A Window into Docker, minikube, and containerd
We are in the endgame now. I promise. From the README, crictl provides a CLI for CRI-compatible container runtimes. The following snippet performs the following:
-
π Manage WebAssembly Apps in WasmEdge Using Docker Tools
Also make sure that you have cri-o, crictl, containernetworking-plugins, and buildah or docker installed.
What are some alternatives?
intel-device-plugins-for-kubernetes - Collection of Intel device plugins for Kubernetes
nfs-subdir-external-provisioner - Dynamic sub-dir volume provisioner on a remote NFS server.
cni - Container Network Interface - networking for Linux containers
SSVM - WasmEdge is a lightweight, high-performance, and extensible WebAssembly runtime for cloud native, edge, and decentralized applications. It powers serverless apps, embedded functions, microservices, smart contracts, and IoT devices.
cfssl - CFSSL: Cloudflare's PKI and TLS toolkit
runc - CLI tool for spawning and running containers according to the OCI specification
rustwasmc - Tool for building Rust functions for Node.js. Combine the performance of Rust, safety and portability of WebAssembly, and ease of use of JavaScript.
smarter
kubernetes - Production-Grade Container Scheduling and Management
descheduler - Descheduler for Kubernetes
containerd - An open and reliable container runtime
wasm-learning - Building Rust functions for Node.js to take advantage of Rust's performance, WebAssembly's security and portability, and JavaScript's ease-of-use. Demo code and recipes.