|
|
|
|
|
|
by drad
2500 days ago
|
|
|
Your main issue will be IO unless you use a host only PV and if you do that you are likely limiting you db instamce to a specific node which can have scaling and/or HA impacts. Most will go with a network based FS to back your db data, if that is the case your network IO will likely impact your db performance. For a dev or test env this might not be a problem but for prod it is usually a blocker. |
|
|
This is exactly what we do, and we're having trouble because of it and not only in terms of scaling the database, but also because it runs on the same node as all other Kubernetes resources. We are considering spinning up a dedicated node for it, but I thought at that point we should probably just buy an actual dedicated database solution instead; buy the expertise we don't have currently.