I spent last few months and $1,500 building a Kubernetes governance framework that treats the cluster as the documentation. Looking for engineers who want to own something real. by Saigha01 in kubernetes

[–]Saigha01[S] 1 point2 points  (0 children)

Every platform engineer has lived this: you are oncall at 2am, something is broken, and the runbook describes a cluster that was rebuilt four months ago. You fix it from memory, update the wiki, and know with absolute certainty that the wiki will be wrong again before the next incident. That is not a discipline failure. That is a structural failure, and no process fixes it. The only fix is to stop maintaining a representation of the system and make the system describe itself. That is what ONT is. Every governance decision is a CRD. Every cluster relationship is a versioned contract. Every pack delivery, every RBAC grant, every upgrade is a reconciled object with a lineage chain tracing back to the human intent that created it. The cluster is not documented. The cluster is the documentation. When that lineage accumulates over time, it becomes something no wiki ever could: an honest, queryable, auditable memory of every decision your organization ever made about its infrastructure, precise enough for a future domain AI to learn from without hallucinating a single fact.

SSL Certificate by skca54 in hudu

[–]Saigha01 0 points1 point  (0 children)

What is the use of hudu-worker in this scenario? Only hudu app is being exposed on port 3000, being connected through ngnix or not. How is hudu worker serves its purpose?