kubeplus
kots
Our great sponsors
kubeplus | kots | |
---|---|---|
38 | 4 | |
602 | 877 | |
2.3% | 0.6% | |
7.9 | 9.7 | |
1 day ago | 6 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.
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
kots
-
Deployment Packaging Solutions
KOTS (by Replicated, mentioned already)
-
packaging a SaaS cloud product
Check out https://kots.io/
-
Ask HN: How would you set up a new B2B SaaS?
We have helped clients several industries and sectors where these words either mean different things, or people who use them are thinking of different things. An appliance has meant a physical thing before it has also meant a VM.
The question you have asked includes a solution. Many client meetings start with that. This is what's called an XY problem[0], where the client says they want want Y, but that's their implementation of a solution to solve X. That may or may not be the only solution, but finding out the actual problem to be solved has never hurt me and saved a lot of time and money.
This is why we spend time defining the problem and stripping away every ounce of jargon we can, because that jargon can create a bias towards a solution that may not be optimal. For example, site-to-site VPN. Why? Gateway ? Why ? These are solutions. What's the job to be done.
Anyway... Have a look at https://www.replicated.com/ and https://kots.io/
- The Biggest and Weirdest Commits in Linux Kernel Git History (2017)
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.
devtron - Tool integration platform for Kubernetes
capsule - Multi-tenancy and policy-based framework for Kubernetes.
operator-lifecycle-manager - A management framework for extending Kubernetes with Operators
labs
porter - Porter enables you to package your application artifact, client tools, configuration and deployment logic together as an installer that you can distribute, and install with a single command.
crossplane - The Cloud Native Control Plane
hauler - Airgap Swiss Army Knife
mongodb-kubernetes-operator - MongoDB Community Kubernetes Operator
OpenFaaS - OpenFaaS - Serverless Functions Made Simple
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
aad-pod-identity - [DEPRECATED] Assign Azure Active Directory Identities to Kubernetes applications.