crobby/norman — explained in plain English
Analysis updated 2026-07-18 · repo last pushed 2026-05-19
Define a Kubernetes custom resource and let Norman generate a working HTTP API around it automatically.
Build a control plane or internal platform on top of Kubernetes without hand-coding API endpoints.
Follow the go-skel example project to see a working skeleton before building your own Norman-based API.
Expose infrastructure choices as consumable APIs for other developers on your team.
| crobby/norman | 0verflowme/alarm-clock | 0verflowme/seclists | |
|---|---|---|---|
| Language | — | CSS | — |
| Last pushed | 2026-05-19 | 2022-10-03 | 2020-05-03 |
| Maintenance | Maintained | Dormant | Dormant |
| Setup difficulty | hard | easy | easy |
| Complexity | 4/5 | 2/5 | 1/5 |
| Audience | ops devops | vibe coder | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires an existing Kubernetes cluster and familiarity with Rancher's API patterns, README is minimal, relies on the go-skel example.
Norman is a toolkit for building APIs that sit on top of Kubernetes. If you're managing infrastructure or building tools that need to work with Kubernetes, this gives you a way to create custom APIs without building everything from scratch. Here's the practical scenario: Kubernetes lets you define custom resources, think of them as new types of objects you can store and manage. Norman takes those custom resources and automatically generates a web API around them. So instead of manually coding HTTP endpoints, you describe what your resource should look like, and Norman handles turning it into a proper API that other tools and applications can talk to. This matters because many teams want to build their own abstractions on top of Kubernetes, and Norman removes a lot of the boilerplate work. The framework was built by Rancher Labs (a company that specializes in Kubernetes management) and follows their specific API design patterns. It's designed for teams who are already deep in the Kubernetes ecosystem and want to extend it with custom functionality. For example, if you're building a platform or control plane on top of Kubernetes, you might use Norman to expose your infrastructure choices as APIs that developers can consume. The README is minimal and points to a skeleton project (go-skel) for concrete examples of how to build with it. If you're considering this, you'd want to check that example project to see whether the approach fits what you're trying to build. It's a specialized tool for a specific use case, rather than a general-purpose API framework.
A Rancher Labs toolkit that auto-generates a web API from Kubernetes custom resources, so teams building infrastructure tools don't have to hand-code API endpoints.
Maintained — commit in last 6 months (last push 2026-05-19).
License is not stated in the available content.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.