Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is it ready for production? #634

Closed
fzyzcjy opened this issue Jul 7, 2023 · 7 comments
Closed

Is it ready for production? #634

fzyzcjy opened this issue Jul 7, 2023 · 7 comments
Labels

Comments

@fzyzcjy
Copy link

fzyzcjy commented Jul 7, 2023

Hi thanks for the operator! I wonder whether it is ready for production?

@ebuildy
Copy link
Contributor

ebuildy commented Jul 10, 2023

well, the 1st release were in 2017 ... so I guess yes

@hashemi-soroush
Copy link
Contributor

hashemi-soroush commented Aug 2, 2023

I've seen a lot of people in the issues section saying they are using it in production heavily.

P.S.: if you believe you got the answer you were looking for, please close the issue.

@fzyzcjy
Copy link
Author

fzyzcjy commented Aug 2, 2023

@hashemi-soroush @ebuildy Thank you for the information! From my experience in other repos, sometimes some people say they use in production, and some people point out small or big problems, so I would like to hear a bit more voices. (e.g. pitfalls to avoid, such as which sub-system is less stable)

@hashemi-soroush
Copy link
Contributor

I understand. Here are a few of the comments I mentioned. You might find a little bit more of what you are looking for in these issues.

  1. Different RedisFailover's sentinels join together #550 (comment)
  2. all Redis replicas terminated at the same time #403 (comment)
  3. Is this project still under maintenance? #315 (comment)
  4. How to set client-output-buffer-limit? #118 (comment)
  5. Operator panicking during critical downtime #122 (comment)

@fzyzcjy
Copy link
Author

fzyzcjy commented Aug 3, 2023

@hashemi-soroush Thank you!

@github-actions
Copy link

This issue is stale because it has been open for 45 days with no activity.

@github-actions github-actions bot added the stale label Sep 18, 2023
@github-actions
Copy link

github-actions bot commented Oct 2, 2023

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants