Release Notes — v1.0¶
Stack version v1.0 marks the general availability of the b'nerd cloud platform, including the first stable release of Workspaces and a coherent set of wired-cloud primitives — compute, networking, DNS, Kubernetes, object storage, managed apps, and the developer toolchain (CLI, Terraform provider, dashboard).
What's new in v1.0¶
Workspaces (GA)¶
Workspaces are ephemeral, scoped development environments that launch inside the b'nerd platform on demand and tear down automatically when their TTL expires.
Highlights:
- Launch modal with access presets — choose Read-only, Reporting, or Developer at launch time. The platform clamps the granted scope to your actual project permissions; a preset can never escalate your access.
- Scoped kubeconfig — a namespace-scoped kubeconfig for your project's target cluster is minted at launch and invalidated when the workspace expires or is revoked.
- Read-only
bnerdAPI token — delivered as~/.bnerd.yamlinside the pod. Developer preset expands the scope to your read/write permissions across the resource groups you hold. - Git clone via personal PAT — Reporting and Developer presets include a clone credential derived from your account git PAT. One PAT per git host, configured once under Account → Git tokens.
- In-grid terminal — the dashboard docks a live terminal directly in the browser without leaving the platform. No public network path to the pod.
- Browser IDE — OpenVSCode Server runs inside the pod and is accessible from the dashboard as a first-party, proxied browser tab.
- Egress opt-in — pods are egress default-deny. Add CIDRs at launch to open specific outbound paths (e.g.
10.0.0.0/8or0.0.0.0/0for full internet access). - Kubernetes access scope — choose
own_namespace(default),namespaced, orcluster-wide kubeconfig scope at launch. The level is clamped to your project grant. - CLI:
bnerd workspace/bnerd ws— full lifecycle management from the terminal:create(launch + attach),launch,attach,list,get,revoke. - TUI:
:wsview — workspaces are a first-class view inbnerd xwith status-filter cycling, attach, and revoke bound to single keys. - TTL ceiling — the launch modal shows only TTL options within your org's ceiling. Custom TTL entry is available; values above the ceiling are rejected.
- Audit log — every workspace action (launch, credential mint, terminal open, editor open, revoke, expiry) is recorded in the organization audit log.
See the Workspaces service reference and the Working with Workspaces guide for full documentation.
Version compatibility matrix¶
All components listed below ship as part of the v1.0 platform release and are validated against each other. Use this release as the baseline for new projects.
| Component | Notes |
|---|---|
| HQ API | v1 (OpenAPI 3.0.1) — single API version; no /v2 path. |
CLI (bnerd) | Full docs: cli.docs.bnerd.com. |
| Terraform Provider | Consume from source or private mirror; public registry publication follows. |
| Dashboard | Requires a valid API token against HQ API v1. |
| S3 Operator | Manages object storage users and buckets via the platform API. |
Public endpoints¶
| Service | Host |
|---|---|
| API | https://api.bnerd.cloud |
| Dashboard | https://app.bnerd.cloud |
| Object storage (S3 / RGW) | https://storage.muc1.de.bnerd.com (region de-muc1) |
| Docs | https://docs.bnerd.com |
Deprecation policy¶
Starting with v1.0 the HQ API v1 is stable. Breaking changes will be introduced only in a new major API version and will be announced with a minimum 90-day migration window. The CLI, Terraform provider, and dashboard will maintain backwards compatibility across patch and minor releases within the v1 series.