|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|👩💻👨💻 Awesome cheatsheets for popular programming languages, frameworks and development tools. They include everything you should know in one single file.|
|Mall Swarm||10,317||9 days ago||43||apache-2.0||Java|
|mall-swarm是一套微服务商城系统，采用了 Spring Cloud 2021 & Alibaba、Spring Boot 2.7、Oauth2、MyBatis、Docker、Elasticsearch、Kubernetes等核心技术，同时提供了基于Vue的管理后台方便快速搭建系统。mall-swarm在电商业务的基础集成了注册中心、配置中心、监控中心、网关等系统功能。文档齐全，附带全套Spring Cloud教程。|
|Kubeshark||9,141||4 days ago||80||apache-2.0||Go|
|The API traffic analyzer for Kubernetes providing real-time K8s protocol-level visibility, capturing and monitoring all traffic and payloads going in, out and across containers, pods, nodes and clusters.. Think TCPDump and Wireshark re-invented for Kubernetes|
|Examples||5,593||8 days ago||3||February 21, 2021||11||apache-2.0||Shell|
|Kubernetes application example tutorials|
|Proxypool||4,411||3 months ago||33||mit||Python|
|An Efficient ProxyPool with Getter, Tester and Server|
|Pipeline||4,160||8 months ago||85||July 18, 2017||1||apache-2.0||Jsonnet|
|PipelineAI Kubeflow Distribution|
|Lilishop||3,496||4 days ago||6||agpl-3.0||Java|
|商城 JAVA电商商城 多语言商城 uniapp商城 微服务商城|
|Redis management tool written in node.js|
|Interview||2,398||4 years ago||1||other|
|Coolstore Microservices||2,215||4 months ago||25||mit||C#|
|A full-stack .NET microservices build on Dapr and Tye|
A Golang based redis operator that will make/oversee Redis standalone and cluster mode setup on top of the Kubernetes. It can create a redis cluster setup with best practices on Cloud as well as the Bare metal environment. Also, it provides an in-built monitoring capability using redis-exporter.
For documentation, please refer to https://ot-redis-operator.netlify.app/
Organizations that are using Redis Operator to manage their redis workload can be found here. If your organization is also using Redis Operator, please free to add by creating a pull request
This operator only supports versions of redis
There are multiple problems that people face while setting up redis setup on Kubernetes, specially cluster type setup. The purpose of creating this opperator is to provide an easy and production ready interface for redis setup that include best-practices, security controls, monitoring, and management.
Here the features which are supported by this operator:-
If you want to deploy redis-operator from scratch to a local Minikube cluster, begin with the Getting started document. It will guide your through the setup step-by-step.
The configuration of Redis setup should be described in CRD definitions. All the examples related to redis standalone and cluster setup can be found inside example folder.
Redis operator requires a Kubernetes cluster of version
>=1.18.0. If you have just started with Operators, it's highly recommended using the latest version of Kubernetes.
The setup can be done by using helm. If you want to see more example, please go through the example folder.
But you can simply use the helm chart for installation.
# Add the helm chart $ helm repo add ot-helm https://ot-container-kit.github.io/helm-charts/
# Deploy the redis-operator $ helm upgrade redis-operator ot-helm/redis-operator --install --namespace ot-operators
After deployment, verify the installation of operator
helm test redis-operator --namespace ot-operators
Creating redis cluster, standalone, replication and sentinel setup.
# Create redis cluster setup $ helm upgrade redis-cluster ot-helm/redis-cluster \ --set redisCluster.clusterSize=3 --install \ --namespace ot-operators
# Create redis standalone setup $ helm upgrade redis ot-helm/redis \ --install --namespace ot-operators
# Create redis replication setup $ helm upgrade redis-replication ot-helm/replication \ --install --namespace ot-operators
# Create redis sentinel setup $ helm upgrade redis-sentinel ot-helm/sentinel \ --install --namespace ot-operators
If you used this just for testing and development purpose you can delete the resources associated with it
# Delete the Redis standalone setup $ helm uninstall redis --namespace ot-operators
# Delete the Redis cluster setup $ helm uninstall redis-cluster --namespace ot-operators
# Delete the Redis replication setup $ helm uninstall redis-replication --namespace ot-operators
# Delete the Redis sentinel setup $ helm uninstall redis-sentinel --namespace ot-operators
# Delete the Redis operator $ helm uninstall redis-operator --namespace ot-operators
If you want to customize the value file by yourself while initializing the helm command, the values files for reference are present here.
To monitor redis performance we will be using prometheus. In any case, extra prometheus configuration will not be required because we will be using the Prometheus service discover pattern. For that we already have set these annotations:-
annotations: redis.opstreelabs.in: "true" prometheus.io/scrape: "true" prometheus.io/port: "9121"
Please see our CONTRIBUTING.md for details.
Please see our CHANGELOG.md for details.
This project is managed by OpsTree Solutions. If you have any queries or suggestions, mail us at [email protected].