INFRAWEAVER ALPHA

infraweaver/catalog

App catalog

Forty-five application definitions ship with the platform. Each is a directory with an application.yaml, optional Helm values and manifests — installable from the console, and readable before you install it.

Everything in the catalog

These are real directory names under kubernetes/catalog/. Nothing here is a logo wall of things that might work one day.

What installing one actually does

  1. You click Install in the consoleOr you copy the directory yourself. The console path is a convenience, not a separate mechanism.
  2. An ArgoCD Application is written and pushed to OnedevThe change is a commit in your own git server, with your account on it. It is reviewable and revertible.
  3. ArgoCD notices within about three minutesOr immediately, if you press sync. It creates the namespace, and Kyverno fits that namespace with a default-deny network policy.
  4. External Secrets materialises whatever credentials it needsGenerated into OpenBao, pulled into the namespace as a real Kubernetes Secret. You never type a password into a values file.
  5. Traefik gets a route and cert-manager already has the certificateThe wildcard covers it, so a new app is reachable over HTTPS without a new certificate request.

ADD YOUR OWN

The scaffold writes the skeleton in the same shape as everything above, so your app is not a second-class citizen next to the shipped ones.

$ bash scripts/new-app.sh my-app

It creates kubernetes/catalog/my-app/ with an application.yaml, an optional values.yaml and a manifests/ directory. Push to Onedev and ArgoCD deploys it. Remember the admission floor: non-root, no privileged containers, capabilities dropped, a real image tag, memory request and limit set.

Feature groups are declarative too

Bigger optional pieces are groups rather than single apps. Flip one and watch platform.yaml rewrite itself, exactly as the console does before committing.

platform.yamlFLIP A FLAG