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

adding guidance for an additional Node Pool #24

Merged
merged 4 commits into from
Oct 16, 2021
Merged

Conversation

dgkanatsios
Copy link
Collaborator

Fixes #17

This PR includes some guidance on how to keep Pods in system namespaces (kube-system/thundernetes-system) and GameServer Pods scheduled in different Nodes, via the addition of a new Node Pool.

docs/FAQ.md Outdated Show resolved Hide resolved
Copy link
Collaborator

@khaines khaines left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great write up on using node selectors to pin the game servers to a particular pool. This can be expanded on as we find more complex scenarios.

Only 1 suggestion on word choice,

@dgkanatsios dgkanatsios merged commit 39f3c8b into master Oct 16, 2021
@dgkanatsios dgkanatsios deleted the additionalnodepool branch October 16, 2021 00:27
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

Successfully merging this pull request may close these issues.

Have system Pods and GameServer Pods scheduled on different Nodes
2 participants