TAK-OS isn't all hardwork and core components. We've also developed a few things just because they are nice, or useful, or just because we could.
Here is a list of components that aren't mandatory, or even core, but might be useful one day.
README
crate-operator turns a namespaced Crate custom resource into a CrateDB StatefulSet and two Services. Kubernetes creates the pods and persistent volume claims from the StatefulSet. These guides follow the checked-in controller and CRD. The deployment template and test fixture use the legacy crate-operator.limbicly.com group. Use the corrected examples in these guides.
README
Keycloak Init is a background initializer for an existing Keycloak installation. It reads the kcadmin and initdata Kubernetes Secrets from one namespace and applies initialization data to one target realm. Start with the user guide to prepare the four initialization files, then follow the administrator guide to provision Secrets and run the service. The guides describe the behavior of init.py. In particular, this service creates missing objects rather than synchronizing changes to existing ones. Newly created realms are disabled until an administrator enables them.
README
TAK-OS Cluster Map displays Kubernetes traffic and ownership relationships in a browser. It reads the cluster through a shared Kubernetes identity and does not modify Kubernetes resources. Start with the user guide if an administrator has already provided a URL. Start with the administrator guide to build or deploy the service. These guides describe the implementation in app/app.py and app/static/index.html. The example manifest is a starting point to adapt to your environment; it is not applied automatically.
README
Orbit Console is a browser dashboard for working with multiple Kubernetes clusters. Register kubeconfigs, select a context, browse resources, inspect ownership, edit or delete objects, and open pod logs or an interactive shell. The application currently targets trusted cluster operators. It has no built-in login, per-user access controls, or Kubernetes read-only mode. All users of an instance can use its registered kubeconfig credentials, subject to Kubernetes RBAC. Administrators must protect access to the service upstream. These guides describe the implementation in this repository. Events, resource creation through the UI, and a raw YAML editor are not currently available.
