-
Notifications
You must be signed in to change notification settings - Fork 816
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
Cannot run GameServer in non-default namespace #146
Comments
This looks like the relevant parts of the log
/cc @dzlier-gcp is there a way we can enable RBAC access to any namespace, or do we have to specify? From the docs, ClusterRoles can access "namespaced resources (like pods) across all namespaces (needed to run kubectl get pods --all-namespaces, for example)" Or am I understanding this incorrectly? |
I get this in the controller logs:
So looks like it's because the agones-sdk service account is created in the default namespace so it's not found in the namespace you try to create the game server in. ClusterRoles are supposed to provide access across clusters, but namespaces are a different matter. I'll look into how to make it work. |
if it's not possible or difficult we could use a variable in the helm chart to prompt for which namespace he wants to use. |
Now enough of #101 has essentially landed - this should be able to be implemented now. Resources |
I want to start by explaining that this came by my fault by creating the gameserver in the agones-system namespace, but anyway, it should be able to run in any namespace.
It makes the gameserver not being able to get an ip and port where to connect to.
(Step 2 on simple-udp example)
Command:
kubectl logs simple-udp-8l26l -c agones-gameserver-sidecar
Logs: https://gist.github.com/jmaeso/aa4562bd3ad4e5c91bd1e558e329f8a7
Workaround for this:
The text was updated successfully, but these errors were encountered: