scylla-operator
opensearch-k8s-operator
scylla-operator | opensearch-k8s-operator | |
---|---|---|
3 | 3 | |
315 | 348 | |
2.2% | 6.3% | |
9.5 | 8.7 | |
6 days ago | 5 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.
scylla-operator
-
TB's of data Load into Cassandra cluster
for orchestration: https://github.com/scylladb/scylla-operator I didn't research bulk load though. I assume the data is on S3?
-
Databases inside or outside k8s cluster?
You can find the ScyllaDB Operator on Github here: https://github.com/scylladb/scylla-operator
-
Project Circe May Update
Scylla’s Operator 1.2 release was published with helm charts (find it on Github; plus read our blog and the Release Notes). Now 1.3 and 1.4 are in the making. In addition, our Kubernetes deployment can autoscale! An internal demonstration using https://github.com/scylladb/scylla-cluster-autoscaler was presented and you are welcome to play with it.
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
What are some alternatives?
argocd-operator - A Kubernetes operator for managing Argo CD clusters.
capsule - Multi-tenancy and policy-based framework for Kubernetes.
scylla-cluster-autoscaler
kubegres - Kubegres is a Kubernetes operator allowing to deploy one or many clusters of PostgreSql instances and manage databases replication, failover and backup.
Scylla - NoSQL data store using the seastar framework, compatible with Apache Cassandra
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.
scylla-stress-orchestrator
tor-controller - Tor toolkit for Kubernetes (Tor instances, onion services and more)
Scylla - Ergonomic mechanical keyboard
custom-pod-autoscaler - Custom Pod Autoscaler program and base images, allows creation of Custom Pod Autoscalers
couchbase-rs - The official, community supported Couchbase Rust SDK
sloth - 🦥 Easy and simple Prometheus SLO (service level objectives) generator