kubeplus
deckhouse
Our great sponsors
kubeplus | deckhouse | |
---|---|---|
38 | 9 | |
607 | 1,010 | |
3.1% | 3.3% | |
7.9 | 9.9 | |
3 days ago | 4 days ago | |
Go | Go | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
kubeplus
- Traditional Shared Hosting on Kubernetes?
-
Kubebouncer - Custom admission controller webhooks
We went through this migration/upgrade in our KubePlus project (https://github.com/cloud-ark/kubeplus). It has an embedded webhook in it, fyi.
-
Is it a good idea to use k8s namespace-based multitenancy for delivering managed service of an application?
You might want to check out - KubePlus (https://github.com/cloud-ark/kubeplus), which has already been referenced in the thread and is exactly designed for building managed application services. I am the originator and core contributor to this project. KubePlus is a Kubernetes Operator that takes an application Helm chart and represents it as a Kubernetes API (CRD) on the cluster. This API allows you to create instances of the application in separate namespaces automatically ensuring a secure perimeter around each instance using NetworkPolicy, Resource Quota, and RBAC. These soft multi-tenancy measures are already mentioned in the thread along with the namespace. KubePlus has automated all of them for you under an API. This API not only allows the creation of the application instances but also supports day-2 operations such as monitoring, troubleshooting, and upgrades to simplify the end-to-end functioning of any managed application service. We are currently seeing interest from teams that want to create managed services for different types of containerized applications, including open-source platforms such as WordPress, Moodle, Ozone/OpenMRS, AI/ML workloads, etc. KubePlus has been tested successfully with all (90+) Bitnami Helm charts. For anyone who wants to deliver a managed application with minimal / no Kubernetes access to their customers, KubePlus can help by accelerating the implementation of namespace-based multi-tenancy on Kubernetes. With the ability to set NetworkPolicy and Resource Quota per application instance, the blast radius is restricted, if something goes wrong in an application instance. KubePlus does not need admin permissions on your cluster. This makes it possible to use KubePlus to manage your application instances on your customer's cluster as well.
-
Writing a Kubernetes Operator
We have an FAQ about Operators here: https://github.com/cloud-ark/kubeplus/blob/master/Operator-F...
It should be helpful if you are new to the Operator concept.
Operators are generally useful for handling domain-specific actions - for example, performing database backups, installing plugins on Moodle/Wordpress, etc. If you are looking for application deployment then a Helm chart should be sufficient.
-
Use Kubernetes to run your SaaS
If you are currently delivering your SaaS as a separate instance of your application per customer, you might want to check out our open-source project KubePlus - https://github.com/cloud-ark/kubeplus
-
Kubernetes for SaaS with multi-instance
A more commerical offering is from Cloudark who have designed a specific solution for operating your Helm application as a SaaS offering. I have never used it (ArgoCD being my poison) but you might find it fits your usecase better
-
Simplest way to host kubernetes with user-level isolation and multi-tenancy
As part of your data platform are you planning to create a separate instance of the database for your end customer? If so, you might find our KubePlus Operator helpful. Check it out here: https://github.com/cloud-ark/kubeplus
-
One user per pod with Kubernetes or other container orchestration tools
We have been helping organizations build such multi-instance multi-tenant cloud-native applications. We start with an application Helm chart and create separate release of it per customer/user of that organization. We have an open source Kubernetes Operator that aids in this: https://github.com/cloud-ark/kubeplus
-
What is your experience with operators?
You might also want to checkout Operator guidelines and Operator FAQ: - Operator Maturity Model guidelines: https://github.com/cloud-ark/kubeplus/blob/master/Guidelines.md
-
Does anybody need a Kubernetes Operator for auto renewing SSL certificates?
The project that is getting some traction recently is our KubePlus Operator that delivers Helm charts as-a-service: https://github.com/cloud-ark/kubeplus
deckhouse
-
K3s – Lightweight Kubernetes
And while k3s sounds easy, it's not after even a slightly larger scale.
If one willing to have in-house k8s today I would recommend https://deckhouse.io/ (I'm not affiliated with them)
-
What's your preferred tool for on-premise k8s installer?
Deckhouse
-
Self-Managed Kubernetes Distributions
Check Deckhouse as well (https://github.com/deckhouse/deckhouse). Cilium integration was added there recently.
-
FOSS News International #3: November 15-21, 2021
Release Deckhouse v1.26.0 · deckhouse/deckhouse (github.com)
-
Which on-prem distribution to use?
Consider Deckhouse as another option that can be installed everywhere: bare metal, private and public clouds. It has an Open Source core offered in Community Edition, but the pricing for Enterprise Edition is also a fit for small companies. All configuration is made via Custom Resources, all routines (like updating Kubernetes versions and related system components) are automated.
-
Does anybody need a Kubernetes Operator for auto renewing SSL certificates?
We use cert-manager in our K8s platform for years and it works perfectly. I don't think there is any chance today to compete with it in terms of community adoption. I also can't find any GitHub links for your project which is the most widely accepted way to become trusted by the community — simply because it covers all the basic needs everyone got used to (in the Open Source world): we can see how the code is developed, we can contribute to it, discuss the issues and concerns we have, etc.
-
Log shipper for Loki
We use Vector to ship logs to different storages (including Loki). You can even find the implementation here, however, I am not sure how useful it might be since it's quite specific (Golang hooks for addon-operator). Our manifests are available there as well.
- Deckhouse is a platform for managing Kubernetes clusters in a fully automatic and uniform fashion. It allows you to create homogeneous Kubernetes clusters anywhere and fully manages them. It supplies all necessary addons to provide observability, security, and service mesh.
- Deckhouse: NoOps Kubernetes platform
What are some alternatives?
vcluster - vCluster - Create fully functional virtual Kubernetes clusters - Each vcluster runs inside a namespace of the underlying k8s cluster. It's cheaper than creating separate full-blown clusters and it offers better multi-tenancy and isolation than regular namespaces.
kubernetes - Production-Grade Container Scheduling and Management
capsule - Multi-tenancy and policy-based framework for Kubernetes.
kubespray - Deploy a Production Ready Kubernetes Cluster
labs
k3s-on-prem-production - Playbooks needed to set up an on-premises K3s cluster and securize it
kots - KOTS provides the framework, tools and integrations that enable the delivery and management of 3rd-party Kubernetes applications, a.k.a. Kubernetes Off-The-Shelf (KOTS) Software.
minikube - Run Kubernetes locally
crossplane - The Cloud Native Control Plane
OpenFaaS - OpenFaaS - Serverless Functions Made Simple
mongodb-kubernetes-operator - MongoDB Community Kubernetes Operator
vector - A high-performance observability data pipeline.