AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
대규모 Grafana Cloud 스택을 스타일 있게 프로비전, 선언형 API와 Argo CD, Crossplane으로 클라우드 관리
Provision Grafana Cloud stacks at scale, with style. Declarative request API, Argo CD owns Git, Crossplane reconciles the cloud.
개발 도구Go · ShellGitHub @rknightion온라인운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
This repository is a portable reference architecture for vending Grafana Cloud stacks through a
small, declarative Kubernetes API. Argo CD owns the objects in Git, Crossplane renders and
reconciles Grafana Cloud resources, and External Secrets Operator (ESO) moves credentials between
Kubernetes and an external secret store. It supports Grafana Cloud only; self-managed Grafana is
out of scope.README 전문 보기 ↗This repository is a portable reference architecture for vending Grafana Cloud stacks through a small, declarative Kubernetes API. Argo CD owns the objects in Git, Crossplane renders and reconciles Grafana Cloud resources, and External Secrets Operator (ESO) moves credentials between Kubernetes and an external secret store. It supports Grafana Cloud only; self-managed Grafana is out of scope.
One vending-machine installation can serve several registered Grafana Cloud organizations. Each
stack selects one immutable organization, region, usage, and platform profile. The baseline gives a
stack rotating administrator and telemetry credentials, deletion protection, starter content, SSO,
reports, plugins, incident relay resources, teams, roles, and content access. The top-level
enabled/ directory starts empty, so copying or installing this repository cannot create a stack
until a user copies an inert catalog example, edits it, reviews the render, and commits the request.
platform.example.orgis a documentation placeholder. Replace it with a domain your organization controls in the XRDs, Compositions, examples, Argo CD health configuration, and requests before adopting this API.
The next release is a breaking one. GrafanaProvisioningRepository requests written against 1.x must be restructured; see Migrating to 2.0. No other request kind changes.
Read Getting started for prerequisites and the copy-edit-review-commit
path to a first request. Use Installation first when the controllers,
provider, secret store, and organization ProviderConfig objects are not already healthy.
Retain protects external objects, not MR-owned in-cluster connection Secrets. Kubernetes garbage
collection removes those Secrets when their managed-resource owners are removed. Before authorizing
any MR removal, operators must prove required Secret retention and consumer handoff; see
the pinned-runtime explanation and removal-approval checklist.
| Page | Covers |
|---|---|
| Documentation home | Who this is for, the request-to-stack flow, baseline capabilities, and the full reading map |
| Core concepts | The Crossplane, GitOps, reconciliation, and ownership terms used by this reference |
| Getting started | Prerequisites and the first request |
| Installation | Direct and Argo CD installation, pins, signatures, releases, and upgrades |
| Configuration | Platform policy, profiles, and the organization registry |
| Architecture | Composition model, renderer registry, resource graph, reconciliation, and provider ownership |
| Request schema | Per-API fields, CompositeResourceDefinitions, short names, admission guards, and status |
| Catalog | Every inert catalog example and its adaptation boundary |
| Secrets | Organization credentials, rotating tokens, ESO, and AWS permissions |
Catalog directories are documented in examples/README.md. The project is available under the Apache License 2.0.
| OAuth and SAML profiles and reconciliation modes |
| Security | Credential boundaries, token models, RBAC, and network restrictions |
| Governance | Token ceilings, bounded product APIs, retention, tenancy, expiry, SCIM scope, and reviewed decommission |
| Migration and adoption | Breaking schema changes per release boundary, and inventory-first, non-destructive adoption |
| Troubleshooting | Recurring reconciliation and validation failures |
| FAQ | Short answers to common questions |