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

gameserver-allocator: helm chart is missing tolerations #901

Closed
daplho opened this issue Jul 12, 2019 · 6 comments
Closed

gameserver-allocator: helm chart is missing tolerations #901

daplho opened this issue Jul 12, 2019 · 6 comments
Labels
area/operations Installation, updating, metrics etc area/user-experience Pertaining to developers trying to use Agones, e.g. SDK, installation, etc kind/bug These are bugs.
Milestone

Comments

@daplho
Copy link
Contributor

daplho commented Jul 12, 2019

While installing agones with helm, I discovered that the gameserver-allocator is missing tolerations. Thus the component can only run on untainted nodes.

@daplho daplho added the kind/bug These are bugs. label Jul 12, 2019
@markmandel
Copy link
Collaborator

/cc @pooneh-m for visibility

@markmandel markmandel added area/operations Installation, updating, metrics etc area/user-experience Pertaining to developers trying to use Agones, e.g. SDK, installation, etc labels Jul 12, 2019
@daplho
Copy link
Contributor Author

daplho commented Jul 13, 2019

PR here: #902

@daplho
Copy link
Contributor Author

daplho commented Jul 15, 2019

here is a new pull request with the correct identity: #910

@pooneh-m
Copy link
Contributor

Thanks @daplho.
@markmandel it seems like there are test coverage missing for this case? Do you have any thoughts on how we could we detect it sooner?

@markmandel
Copy link
Collaborator

markmandel commented Jul 15, 2019

Ooh! That's a good question. So right now the e2e cluster doesn't actually have a nodepool split between system components and gameservers - it's just one big default nodepool.

So I see two options, basically as addition to e2e tests:

  1. Create a nodepool specifically for everything in agones-system. Write an e2e test that checks that every pod in agones-system namespace is in the right nodepool.
  2. Check every pod in agones-system to ensure it has the correct toleration applied.

No.1 checks the result, No.2 checks the implementation. Maybe both?

@markmandel
Copy link
Collaborator

Closing - we will create a new ticket for testing toleration in our e2e tests.

@markmandel markmandel added this to the 1.1.0 milestone Sep 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/operations Installation, updating, metrics etc area/user-experience Pertaining to developers trying to use Agones, e.g. SDK, installation, etc kind/bug These are bugs.
Projects
None yet
Development

No branches or pull requests

3 participants