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

Add ability to exclude a server from acting as a database server in a cluster #1440

Open
stgraber opened this issue Nov 29, 2024 · 0 comments
Labels
Feature New feature, not a bug
Milestone

Comments

@stgraber
Copy link
Member

The main use case for this is when running a cluster that's got a mix of physical servers and virtual machines as cluster members. This is somewhat common for security reasons where you want a single unified control plane but don't want containers running directly on bare metal, so you create a few VMs that themselves run Incus and are joined into the cluster, then containers get scheduled within those VMs.

The problem with that setup is that those VMs may get elected to run the Incus database, allowing for the situation where both a VM and its host are both database voters. Losing that physical server would then take out a majority of the database voters and end up breaking the database.

We should introduce some kind of cluster role, like database-client which then prevents the affected cluster member from getting elected to voter or stand-by within the cowsql cluster.

@stgraber stgraber added the Feature New feature, not a bug label Nov 29, 2024
@stgraber stgraber added this to the soon milestone Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature, not a bug
Development

No branches or pull requests

1 participant