kubeplus
crossplane
Our great sponsors
kubeplus | crossplane | |
---|---|---|
38 | 60 | |
595 | 8,559 | |
2.9% | 3.9% | |
7.9 | 9.9 | |
about 1 month 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?
Thanks for the pointer. As per this document, 'Multi-customer tenancy' seems to be the closest to the managed/hosted application use case. Has anyone used KubePlus solution referenced here?
Yeah, any pointers for the challenges you faced, or any additional case study documentation will be helpful. Do you think solution like https://github.com/cloud-ark/kubeplus can be useful to simplify automation?
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.
-
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
-
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
-
Feedback wanted on pod resource metrics before GA promotion
When you say capacity planning, can you elaborate on some use-case(s) that are being targeted with this feature? Is the idea that knowing the actual usage directly from the scheduler can help deployers, either from outside the cluster or in-cluster via GitOps, make informed decisions such as configuring node selectors on any future Pods? The reason I ask this is - in our project (KubePlus - https://github.com/cloud-ark/kubeplus ) we support Node selector policies at Helm chart level. This enables, for example, to create a Helm release on a specific worker node. Currently KubePlus is not using any metrics data to decide whether a particular node has enough spare capacity to accommodate the incoming Helm release. If the Pod metrics are available from the scheduler then we can correlate those with the nodes on which the Pods are running and then decide whether a node has enough remaining capacity to support the resources of the Helm release.
crossplane
-
Rethinking Infrastructure as Code from Scratch
did anyone adopt in production https://crossplane.io ?
-
Understanding Crossplane is being hard
- https://github.com/crossplane/crossplane/blob/master/design/one-pager-composition-environment.md
-
Automated provisioning for data resources
In the overall scheme of things , look at services like backstage.io , crossplane.io and opslevel.com to get ideas. This is not necessarily an endorsement of the services. If all you want is to handle cloud resources and that's it, Terraform can be enough with what ever flavor of web technologies you and your team are comfortable with and can support it along the way. Doesn't take much to create a js based website to collect data from a form, or use other means to collecting data as long as its recorded and transparent for accountability.
- What are some Terraform automation tools you want to exist?
- Anyway to automate the AKS cluster creation using Yaml?
-
One multi-container deployment vs. a separate deployment for each image?
Practically, you'll be replacing stock k8s resources (deployments) with custom ones like Argo Rollouts with Keda autoscaling, so you have to plan the respective Gitops CD pipeline (fluxcd/argocd with some crossplane), as well.
- What is the coolest Go open source projects you have seen?
-
Kubernetes and Helmfile Best Practices
assess https://crossplane.io/
-
Question on how to handle common infrastructure services;
Also, 5 cents * assess https://crossplane.io/ * dont use terraform, ansible or other stone age stuff in k8s * dont call fluxcd or argo gitops, those 2 companies are just exploiting the practice name.
-
Ask HN: Have You Left Kubernetes?
Crossplane [1] is great way to create and manage resources across cloud providers, MSPs via kubernetes objects.
What are some alternatives?
kubevela - The Modern Application Platform.
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
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.
terraform-cdk - Define infrastructure resources using programming constructs and provision them using HashiCorp Terraform
helm - The Kubernetes Package Manager
external-dns - Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services
istio - Connect, secure, control, and observe services.
kubefed - Kubernetes Cluster Federation
tofu-controller - A GitOps OpenTofu and Terraform controller for Flux
karmada - Open, Multi-Cloud, Multi-Cluster Kubernetes Orchestration
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
terraform-provider-aws - Terraform AWS provider