-
Notifications
You must be signed in to change notification settings - Fork 252
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
[Docs]: guide on production readiness for CNPG #4428
Comments
I think we should be careful here as "production readiness" might vary from environment to environment. I am hesitant to provide any sort of checklist at Community level, as that might be interpreted as an exhaustive list of suggestions or recommendations. What if we forget something? I'd hate in 12 months having to deal with somebody saying: "Well, I followed all your recommendations". Also, to what extent it will relate to running Postgres? or to just Kubernetes? I think we should encourage third-party organizations or individuals to take the initiative here, as I don't think as a Community we have the strength and the resources to then respond to enquiries and discussions. For example, not even Postgres has that information in the documentation. Just my two cents. For me this is -1. |
Those are good points. Yes, probably right, better left to individuals or third parties. |
Is there an existing issue already for your request/idea?
What problem in the existing documentation this issue aims to solve?
There is no discussion on the minimum checklist for what would be
a "production ready" CNPG installation.
We see people using CNPG in production that don't have backups.
We see some PostgreSQL newbies running CNPG clusters that don't
have any monitoring....
Describe what additions need to be done to the documentation
We should have a new page guiding users to production readiness.
Describe what pages need to change in the documentation, if any
No response
Describe what pages need to be removed from the documentation, if any
No response
Additional context
No response
Backport?
Yes
Code of Conduct
The text was updated successfully, but these errors were encountered: