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

What are the risks and downsides of using cn on production? #132

Open
n1kio opened this issue Feb 19, 2021 · 1 comment
Open

What are the risks and downsides of using cn on production? #132

n1kio opened this issue Feb 19, 2021 · 1 comment

Comments

@n1kio
Copy link

n1kio commented Feb 19, 2021

I see that you don't recommend it, but I would like to understand why to evaluate for my specific use case (small on-premise deployments of an s3 object storage that won't need to scale much if at all).

@leseb
Copy link
Member

leseb commented Feb 25, 2021

I guess today it's not recommended simply because it's not maintained anymore. Also, we never switched to use #108 instead of the demo.sh script. It's not a huge problem though.
Also, we have seen the pod getting more and more memory and crashing every now and then.

But it really boils down to the support I would say.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants