microshift
IngressMonitorController
Our great sponsors
microshift | IngressMonitorController | |
---|---|---|
9 | 1 | |
630 | 547 | |
2.5% | 3.1% | |
9.9 | 8.5 | |
6 days ago | 3 days 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.
microshift
- Microshift: Small form factor OpenShift/Kubernetes
- new MicroShift releases [4.12.x]!
-
Running Kubernetes on Raspberry Pi 4 8GB
Another good option is Microshift: https://github.com/openshift/microshift
-
Install k8s on single node bare metal
RPM RHEL derivatives I recommend: https://microshift.io
-
Manage Multiple Kubernetes Clusters with ArgoCD
If you are moving to edge you can try microshift (https://microshift.io/). There is also option to run a single node ocp (https://docs.openshift.com/container-platform/4.9/installing/installing_sno/install-sno-installing-sno.html).
-
OpenShift is open source, is OpenShift Local too?
There is also microshift. https://microshift.io/
-
How many use snap on fedora?
I use one snap, but not on Fedora, instead with RHEL. It is the only way to use Microk8s, which is a quite full-featured distribution of Kubernetes that has a small footprint. Red Hat recently came out with an early offering called MicroShift, but it's not really ready yet. When it can satisfy my needs, you'll bet I'm switching.
-
MicroShift
This is an open source project from the start (as most things red hat creates), you can find the coffee here: https://github.com/redhat-et/microshift
-
Aperçu de Microshift, une implémentation légère d’OpenShift …
GitHub - redhat-et/microshift: A small form factor OpenShift/Kubernetes optimized for edge computing
IngressMonitorController
-
Kubernetes operator that automates uptime monitoring of your ingresses
Any benefits to using this over https://github.com/stakater/IngressMonitorController ?
What are some alternatives?
Openshift Origin - Conformance test suite for OpenShift
apisix-ingress-controller - APISIX Ingress Controller for Kubernetes
microk8s - MicroK8s is a small, fast, single-package Kubernetes for datacenters and the edge.
k8s-bigip-ctlr - Repository for F5 Container Ingress Services for Kubernetes & OpenShift.
okd - The self-managing, auto-upgrading, Kubernetes distribution for everyone
dex-k8s-authenticator - A Kubernetes Dex Client Authenticator
microk8s - MicroK8s is a small, fast, single-package Kubernetes for developers, IoT and edge. [Moved to: https://github.com/canonical/microk8s]
khelm - A Helm chart templating CLI, kustomize plugin and containerized kustomize/kpt KRM function
kubeedge - Kubernetes Native Edge Computing Framework (project under CNCF)
kubernetes-ingress-controller - :gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.
runtime - Kata Containers version 1.x runtime (for version 2.x see https://github.com/kata-containers/kata-containers).
tronitor - Bash script to work with UptimeRobot, StatusCake, HealthChecks.io, & Upptime monitoring providers