kubeplus
porter
Our great sponsors
kubeplus | porter | |
---|---|---|
38 | 8 | |
607 | 1,149 | |
3.1% | 3.3% | |
7.9 | 8.9 | |
1 day ago | 4 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
porter
-
Stronger abstraction for deployments
This is just a concept. AFAIK only one implemented this concept is Microsoft's project porter: https://github.com/getporter/porter
-
New automation tool - kuberlogic
For porter I am talking about this project https://porter.run/ and NOT this https://porter.sh/
-
Deployment Packaging Solutions
Porter
-
kbrew: Install any complex app on Kubernetes with one step - within the context of your environment. Please check out, would love feedback!
As far as I know the tool is used at least in Microsoft. The classic use case is where you want to install an application and also define the infrastructure as well (i.e cluster + db + lb + app). You can see the examples here https://github.com/getporter/porter/tree/main/examples
-
k8s based platform
Check https://cnab.io/ and https://porter.sh/
-
Terraform 1.0 Release
I'm closely tracking an effort by Microsoft that aims to do a lot of what you're describing since I find myself bridging between these tools and deploying stacks that span tools and roles. [CNAB](https://cnab.io/) and the front-running implementation, [Porter](https://porter.sh/), enable one-step infra deployments, packaged as a single OCI-compatible container, with any number of steps, using the best tools for each of those steps. Think of using aws-cli for some initialization step (create or verify presence of a state bucket), applying some terraform to create infra, and finishing with a helm chart to complete deployment of app components. Each stage in a bundle packages not only the code to run it but also the execution binary of the tool that runs it. The spec and porter are still a moving target but it's a promising space and a nice adjacent evolution of the current state of tooling.
-
Open source Heroku Like Platform on premises
Cool, it's great to know that it isn't abandoned.
I'm not sure why you'd say that their business model was a success. They were bought by Microsoft for Azure. I guess I wonder if a PaaS company can survive without getting the profits off renting the machines to people. Amazon, Google, and Microsoft all have PaaS options based around the idea that it comes bundled with the compute, not as a standalone open-source thing for you to use on any platform.
I guess the question is whether Porter's business plan is "make enough that a company that owns a cloud wants to buy us". Oracle could probably use a nice PaaS platform and team. Maybe DigitalOcean would like to beef up their PaaS offering by acqui-hiring a team with proven knowledge.
Poking around https://deislabs.io, it's interesting to see that they have a project called "Porter" which seems to be unrelated to the "Porter" being launched here: https://porter.sh. They aren't quite the same, but they both have "easily run your app" goals.
-
Make Kubernetes as easy as Heroku. Open source PaaS to deploy Docker containers on a Kubernetes cluster running in YOUR OWN cloud provider.
There is already this from Microsoft https://github.com/getporter/porter
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.
CapRover - Scalable PaaS (automated Docker+nginx) - aka Heroku on Steroids
capsule - Multi-tenancy and policy-based framework for Kubernetes.
helm-charts - Komodor.io public helm charts
labs
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
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.
porter - Kubernetes powered PaaS that runs in your own cloud.
crossplane - The Cloud Native Control Plane
pulumi-terraform-bridge - A library allowing providers built with the Terraform Plugin SDK to be bridged into Pulumi.
mongodb-kubernetes-operator - MongoDB Community Kubernetes Operator
kapp-controller - Continuous delivery and package management for Kubernetes.