-
Notifications
You must be signed in to change notification settings - Fork 70
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
Support Nixery deployments inside of Kubernetes clusters #4
Comments
There does not seem to be a clean way of doing this that works across all Kubernetes clusters using something like Some discussions with people revealed that there's also no good definition of what "clean" means in this context. Here's a very raw list of issues:
I will set up guides and examples for how to do this that focus specifically on GKE. Other users might want to contribute equivalent guides for other Kubernetes hosters. |
My personal infrastructure repository (tazjin/depot) now features a Nixery deployment inside of Kubernetes (see here). A similar setup to this should be documented in the Nixery docs for people to experiment with. The network setup basically involves a private DNS zone for the GCP VPC (in which the cluster pool(s) run) that points |
@tazjin Maybe you could give loose input to: |
Several open questions around caching, internal addressing etc. remain here - more information coming soon.
The text was updated successfully, but these errors were encountered: