II.
Topic JSON
Structured · livetopic:kubernetes-native-forge
Kubernetes-Native Git Forge json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "topic:kubernetes-native-forge",
"_kind": "Topic",
"_file": "domain/products/krate.yaml",
"_cluster": "domain",
"attributes": {
"displayName": "Kubernetes-Native Git Forge",
"description": "The architectural thesis that a Git collaboration platform (forge) should\nbe built as a native extension of the Kubernetes API rather than as a\nstandalone application deployed on Kubernetes. All forge concepts —\nrepositories, pull requests, issues, pipelines, users, teams, RBAC — are\nmodeled as Kubernetes custom resources or aggregated API objects. This\nmeans kubectl, client-go, and any Kubernetes-native tooling can interact\nwith the forge directly. The platform inherits Kubernetes' authn/authz,\nadmission control, and controller reconciliation patterns, eliminating\nthe need for a parallel identity and permission system.\n"
},
"outgoingEdges": [
{
"from": "topic:kubernetes-native-forge",
"to": "domain:platform-engineering",
"kind": "applies_to"
},
{
"from": "topic:kubernetes-native-forge",
"to": "domain:devops",
"kind": "applies_to"
},
{
"from": "topic:kubernetes-native-forge",
"to": "domain:software-engineering",
"kind": "applies_to"
},
{
"from": "topic:kubernetes-native-forge",
"to": "topic:gitops-principles",
"kind": "related_to"
}
],
"incomingEdges": [
{
"from": "domain:platform-engineering",
"to": "topic:kubernetes-native-forge",
"kind": "contains",
"attributes": {
"notes": "Core architectural pattern for K8s-native Git forges"
}
}
]
}