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.

Sign up for GitHub

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

Jump to bottom

[Docs]: guide on production readiness for CNPG #4428

Open
2 tasks done
jsilvela opened this issue May 3, 2024 · 2 comments · May be fixed by #4429
Open
2 tasks done

[Docs]: guide on production readiness for CNPG #4428

jsilvela opened this issue May 3, 2024 · 2 comments · May be fixed by #4429
Assignees
@gbartolini
Labels
triage Pending triage

Comments

@jsilvela
Copy link
Collaborator

jsilvela commented May 3, 2024

Is there an existing issue already for your request/idea?

  • I have searched for an existing issue, and could not find anything. I believe this is a new documentation enhancement to be evaluated.

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

  • I agree to follow this project's Code of Conduct
@jsilvela jsilvela added the triage Pending triage label May 3, 2024
@jsilvela jsilvela linked a pull request May 3, 2024 that will close this issue
Open
@gbartolini
Copy link
Contributor

gbartolini commented May 4, 2024 •
edited

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.

@jsilvela
Copy link
Collaborator Author

jsilvela commented May 5, 2024

Those are good points. Yes, probably right, better left to individuals or third parties.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gbartolini gbartolini

Labels
triage Pending triage
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

docs: add a Production Readiness guide cloudnative-pg/cloudnative-pg
2 participants
@gbartolini @jsilvela