Skip to content

Lack of documentation. #1076

Open
Open
@hedgss

Description

@hedgss

Hi,

I see that postgres-operator, Spilo documentation doesn't cover some important topics:

  • Matrix compatibility. I know, it is always a lack of resources. But in any case, you test your releases and it'd be good to share more information.
    • Postgres-operator and kubernetes version. What versions were tested and compatible?
    • Postgres-operator and spilo images. What versions can be used together?
  • Upgrade guide. No information about the upgrade process, what issues can happen. How to fix them, etc. Common errors, issues and pitfalls.
    No suggestions on how to handle breaking changes.
  • No information about what exactly required by postgres-operator to be able to manage patroni inside Spilo.
    What information is stored in etcd. How postgres-operator sends requests to patroni, how patroni authorize it.
  • Share more information about your best practices that can include a lot of topics, such as
    • backups & restore
    • monitoring
    • replication configuration
    • etc

I think the list of questions is much longer, but these are the questions that I faced.
I think it'd be useful for the rest as well.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions