-
Notifications
You must be signed in to change notification settings - Fork 8
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
default router #110
default router #110
Conversation
I'm planning to return to this effort in the near future. |
This is an important piece of the compacted K8s deployment story that supports self-hosted zrok and bring-your-own-k8s user stories. |
e473bdb
to
3684457
Compare
My plan for this is to administratively create a router named like "default-router" when the controller is deployed. The router enrollment token and any required config inputs should be stored in a k8s secret or configmap with a predictable name so that it's practical to orchestrate deploying a router chart to source that token and config as template inputs. |
This won't unblock anything, and it better accomplished by an operator. |
resolves #108