-
Notifications
You must be signed in to change notification settings - Fork 90
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
On multi-node Kubernetes, the default settings on ReadWriteOnce without pod affinity are non-functional #17
Comments
This same problem also spans to the Job However, there the Helm chart includes function to set Similar setting should be added to |
Added an in-progress PR here: #13 |
Hi, have you tried setting the persistence as ReadWriteMany? I ask because I'm setting up a single-node cluster for now but will shift to multi-node in a second moment and I'd like to avoid running into this pitfall. And I don't know if setting ReadWriteMany can work to have multiple pods with Sidekiq and Rails instances possibly not staying on the same pods like it happened to you. |
ReadWriteMany works, but of course requires support for it from the storage class. Alternatively you can force the pods to co-locate, which kind of moots the point of having a multi-node cluster in the first place. |
Steps to reproduce the problem
They are waiting to mount the persistence volumes system and assets. These can only be mounted on a single node at a time.
Expected behaviour
Everything should work on roughly default settings
Actual behaviour
The pods hang in ContainerCreating state in a difficult to understand way.
Detailed description
The default settings are non-functional on multi-node clusters. Either there needs to be a better comment warning to set pod affinities, the default mode should be ReadWriteMany, or there should be a pod affinity defined which puts these two kinds of pods to the same nodes by default.
Specifications
Mastodon: edge
OS: Ubuntu
Kubernetes: MicroK8S
Nodes: 2+
The text was updated successfully, but these errors were encountered: