Manifests
Deployed and supported. The fields and commands described here are stable within version v1alpha1.
A manifest is a YAML document with apiVersion, kind, metadata.name, and spec.
All kinds are at version v1alpha1. This section documents each kind field by field, with
the observed status, the conditions, and common errors.
metadata only holds name. Do not specify a tenant: it is inferred from your session.
Labels, annotations and any other metadata key are rejected.
Kinds applied with sng apply
These are the manifests you write and version. They go through
sng apply, which validates them (consistency rules included) before
saving them to your tenant's desired state.
| Kind | Group | Role | Status |
|---|---|---|---|
| App | deploy.stackngo.io | Services, jobs, cronjobs, docker compose style | Available |
| SSMSecret | ssm.stackngo.io | Secret declared, generated, and rotated by the platform | Available |
| CDNSite | cdn.stackngo.io | Static site served from a bucket | Available |
| IAMApplication | iam.stackngo.io | OIDC client for your own applications | Available |
| IAMRole | iam.stackngo.io | Role for your end users | Available |
| IAMGroup | iam.stackngo.io | Group for your end users | Available |
| RegistryRepository | registry.stackngo.io | OCI image repository | Available |
| RegistryAccessKey | registry.stackngo.io | Registry access key, to pull or push images | Available |
| DNSZone | dns.stackngo.io | Domain you bring | Beta |
| DNSRecord | dns.stackngo.io | DNS record in one of your zones | Beta |
| Monitor | monitoring.stackngo.io | HTTP, TCP, ICMP, or DNS uptime probe | Beta |
| NotificationChannel | monitoring.stackngo.io | Alert destination | Beta |
| StatusPage | monitoring.stackngo.io | Public status page | Beta |
| MaintenanceWindow | monitoring.stackngo.io | Scheduled maintenance window | Beta |
Kinds managed by the identity API
These resources describe permissions. You do not write them yourself: they are produced by
sng tenant policy and sng tenant oidc (or the /v1/iam/* routes), and the platform saves
them to your tenant's desired state. The reference pages help you read what was created and
understand its effect.
| Kind | Group | Role | Status |
|---|---|---|---|
| IAMPolicy | iam.stackngo.io | Permissions document (Allow/Deny, actions, resources) | Available |
| IAMPolicyBinding | iam.stackngo.io | Attaches a policy to users, roles, machines, trusts | Available |
| IAMOIDCTrust | iam.stackngo.io | Federation of an OIDC provider (CI) | Beta |
Upcoming kinds
The interface is published to gather your feedback. Nothing can be applied yet.
| Kind | Group | Role | Status |
|---|---|---|---|
| Workspace | tofu.stackngo.io | OpenTofu module applied from the tenant | Coming soon |
| Provider | tofu.stackngo.io | Configuration of an OpenTofu provider | Coming soon |
| GeneratedAPI | apibuilder.stackngo.io | Go API generated from models | Coming soon |
| Model, View | apibuilder.stackngo.io | Building blocks of a generated API | Coming soon |
| MailProvider, MailUser, MailTemplate | mail.stackngo.io | Sending e-mails: SMTP server, sender, template | Beta |
Reading a reference page
All pages follow the same outline: what it is for, a minimal example, a complete annotated
example, the fields table (generated from the code, so always up to date), the cross-field
validation rules, status and conditions, what happens when you delete, and common errors. The
common conventions explain what you will find everywhere: conditions,
observedGeneration, deletion policies.