opensearch-k8s-operator
capsule
Our great sponsors
| opensearch-k8s-operator | capsule | |
|---|---|---|
| 3 | 5 | |
| 344 | 1,455 | |
| 5.2% | 3.0% | |
| 8.7 | 9.3 | |
| 7 days 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.
opensearch-k8s-operator
-
How to Install OpenSearch on Kubernetes (Using HELM charts)
Or use the OpenSearch Kubernetes Operator to spin up and manage your new clusters: https://github.com/Opster/opensearch-k8s-operator
-
OpenSearch Kubernetes Operator
The Kubernetes Operator for OpenSearch is here! The open-source Apache 2.0 Operator is used for automating the deployment, provisioning, management, and orchestration of OpenSearch clusters and OpenSearch dashboards. Check out the github repo and give it a spin here: https://github.com/Opster/opensearch-k8s-operator
-
Moving to elastic.co managed - what settings / control do we lose ?
Because of these limitations and the ones others highlighted, you might be better off staying self-managed. A Kubernetes deployment could be a good alternative to the managed service route. You can check out this K8s Operator: https://github.com/Opster/opensearch-k8s-operator
capsule
-
Multi-tenancy in Kubernetes
Capsule
-
How we reduced Kubernetes Clusters Sprawl by adopting Vclusters: An Introduction
At the end is just a tool which helps to achieve multi tenancy(with all pros and cons) in Kubernetes. It takes a different approach from capsule for example as you have a dedicated control plane for each tenant which means you have an isolated api server that you can spin up in a matter of seconds and lets you also achieve better resource utilizations by using the same nodes shared among all tenants
- Is it anti-pattern to have multiple environments under a single namespace?
-
k8s based platform
For multi tenancy you could use this: https://github.com/clastix/capsule
- RBAC for developer self-service?
What are some alternatives?
scylla-operator - The Kubernetes Operator for ScyllaDB
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.
kubegres - Kubegres is a Kubernetes operator allowing to deploy one or many clusters of PostgreSql instances and manage databases replication, failover and backup.
kiosk - kiosk 🏢 Multi-Tenancy Extension For Kubernetes - Secure Cluster Sharing & Self-Service Namespace Provisioning
metering-operator - The Metering Operator is responsible for collecting metrics and other information about what's happening in a Kubernetes cluster, and providing a way to create reports on the collected data.
kamaji - Kamaji is the Hosted Control Plane Manager for Kubernetes.
tor-controller - Tor toolkit for Kubernetes (Tor instances, onion services and more)
hierarchical-namespaces - Home of the Hierarchical Namespace Controller (HNC). Adds hierarchical policies and delegated creation to Kubernetes namespaces for improved in-cluster multitenancy.
custom-pod-autoscaler - Custom Pod Autoscaler program and base images, allows creation of Custom Pod Autoscalers
kubeplus - Kubernetes Operator to create multi-instance SaaS from Helm charts using Kubernetes-native APIs
sloth - 🦥 Easy and simple Prometheus SLO (service level objectives) generator
loft - Namespace & Virtual Cluster Manager for Kubernetes - Lightweight Virtual Clusters, Self-Service Provisioning for Engineers and 70% Cost Savings with Sleep Mode