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

Set VolumeMount to ReadOnly=true explicitly for DB replica pod for /pgdata #20

Closed
vladimirvivien opened this issue Jun 22, 2017 · 1 comment

Comments

@vladimirvivien
Copy link
Contributor

vladimirvivien commented Jun 22, 2017

The documentation mentions that the replica pod for the database is read-only. However, when inspecting the pod, it shows that the readOnly flag is set to false.

Volumes:
  pgdata:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	pgcluster-pvc
    ReadOnly:	false

Would it make sense to also set the volume bind-mount to readOnly for the pod container or would that break the normal DB operation ?

@jmccormick2001
Copy link
Contributor

with the replica being able to be promoted to a read-write master (recovery) it would need to be set to read/write, so essentially doing it this way supports a future 'failover' command, it will work sort of like this: "pgo failover mycluster', when a user enters that command it will find a replica and trigger the failover to it plus a whole lot of other stuff :^)) hope that helps.

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