TAK-OS follows a component model architecture, which means we aim to have one tool perform one task well, rather than having complex, multi-function monoliths that are hard to replace, and hide there operating state and details.
We also aim to have all products documented in their source repositories, but also for that documentation to be published here each time a new release is tagged.
- TAK-OS BootISO
The first part of TAK-OS most people will see is the ingregrated installer on the BootISO installation media.
- TAK-OS Ingress
With the discontinuation of ingress-nginx, a very real gap has opened up in the Kubernetes ecosystem. In addition, the Kubernetes team have decided to develop a new way of bringing traffic to your application - the Gateway API. This all has the potential to become unnecessarily complicated. Rather than waiting for someone else to fill these gaps, I decided to build something deliberately small, fast, and standards-faithful (All of them!).
- TAK-OS KubeUP
Create your cluster fully self contained. Cluster up, add, remove or replace nodes transparently.
- TAK-OS Orbit Deploy
The problem with Kubernetes automation, one of the problems with Kubernetes automation, because there are many, is that of whose opinion you are going to choose instead of your own.