-
Notifications
You must be signed in to change notification settings - Fork 3
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
K8s Operator for Tinkerbell Stack Management #9
Comments
@chrisdoherty4 can you please assign this to me |
@moadqassem What ideas do you have? I know we talked provisionally on some internal work you'd done. Have there been any further developments? We haven't formally accepted this ticket, perhaps we could talk about it in tomorrow's call. |
@chrisdoherty4 Yeah there was some work done in the past about this. The original code had some building blocks from our internal repos and I stripped that away to have it full generic/open source. The current code is kinda an MVP(it deploys tink-stack in any k8s cluster and make sure it follows the operator design/reconciling pattern). Regarding further development, we can do the handover to the TB community maybe mid of March as I need to have some last touches and then I can present it. Tomorrow I can shed more light to it. |
New repository created at https://github.com/tinkerbell/operator. The repository is currently experimental and we intend on maintaining an experimental status while we explore the feasibility of an operator and understand the challenges it solves for us. |
The Tinkerbell stack is a set of containers that could be managed by a Kubernetes operator. Initial stack deployment is reasonably trivial but it becomes more complex with stack upgrades. We have seen instances where users are instrumenting their own logic to perform Tinkerbell stack management.
The text was updated successfully, but these errors were encountered: