k8s container runtimes
-
Updated
Oct 18, 2020
k8s container runtimes
This project aims to provide a basic Kubernetes Cluster (for development/study purposes).
Design of a distributed system for exploit scheduling and execution, and flag submission in "Attack and Defense" CTF competitions.
CentOS as a grunt/worker node to EKS
Installs OpenShift Origin on a Vagrant managed VM with CentOS 7
Install CRI-O on a RHEL/CentOS or Debian/Ubuntu server.
This repository provides a guide for deploying Kubeflow on a self-managed Kubernetes cluster set up on bare metal hardware, enabling you to leverage the processing power of GPUs available on worker nodes. CRI-O, a lightweight alternative to Docker, is utilised as the container runtime engine.
Kubernetes cluster setup using kubeadm & container runtime environment as CRI-O
An operator for automating nri-plugins deployment.
Install Kubernetes v1.25.4 on Fedora CoreOS 37 automated with ignition, ansible and kubeadm
Kubernetes Vagrant node (master/worker) for local testing with CRI-O, Calico, WireGuard, Ingress Nginx and OpenEBS
Fully automated deployment of a k8s 1.21+ cluster with no dockershim
Configs and scripts for bootstrapping an opinionated Kubernetes cluster anywhere.
An ansible role to install cri-o CRI on your Kubernetes nodes. Currently, only Debian10 nodes are supported by this project.
High-level overview of Containers and Container Orchestration
Deploy cri-o from source using Ansible
Add a description, image, and links to the cri-o topic page so that developers can more easily learn about it.
To associate your repository with the cri-o topic, visit your repo's landing page and select "manage topics."