@gapi/gcli 1.8.247 → 1.8.248

package/AGENTS.md

@@ -92,6 +92,10 @@ This repo is documentation-driven. With every change:
 3. **Skills / AGENTS.md** - learned something non-obvious, or a workflow
    bit you? Update the owning skill (`.agents/skills/<name>/SKILL.md`) or
    this file in the same change.
+4. **User docs + What's new** - a change users can see or do also updates
+   gql-fission's public docs page (`gql-fission/src/docs/<slug>.md`) and adds a
+   line to `gql-fission/src/app/changelog/releases.ts`. Skill:
+   `user-docs-and-changelog` in gql-fission.
 
 Before working on an existing feature: `node scripts/changelog.mjs render
 --feature <slug>` + its feature doc. That is where "how to test" and "how

package/README.md

@@ -211,6 +211,27 @@ Steps that remove capacity or release the load balancer's IP (going back to
 `singleNode: true`, `loadBalancer: false`) are skipped unless you pass
 `--yes`. Nodes and the load balancer are billed per started hour.
 
+#### Virtual clusters
+
+A virtual cluster has its own Kubernetes API and Fission but no servers: it
+runs in one namespace of the shared Lambforge cluster, or of one of your
+private clusters, and is ready in about two minutes. Everything else
+(environments, lambdas, `--clusterName`, `cluster:kubeconfig`,
+`cluster:teardown`) works the same as for a private cluster; scaling and
+load balancer commands don't apply.
+
+```bash
+gcli cluster:create --virtual --name dev                  # on the shared cluster
+gcli cluster:create --virtual --name stage --host prod    # on your private cluster "prod"
+```
+
+```yaml
+cluster:
+  name: dev
+  provider: vcluster
+  host: prod          # optional - omitted = the shared cluster
+```
+
 ### RabbitMQ Brokers
 
 A project may have several RabbitMQ brokers, each optionally scoped to one of its private clusters.

package/docs/changelog.d/2026-10-27-virtual-clusters-cluster-create-virtual-and-provider-vcluster-in-cluster-appl.md

@@ -0,0 +1,18 @@
+## 2026-10-27 - virtual-clusters: cluster:create --virtual and provider vcluster in cluster:apply
+
+**Feature:** virtual-clusters · **Type:** feat
+
+- `cluster:create --virtual [--host <private-cluster-name>]` and, in the
+  `cluster:` section, `provider: vcluster` + `host:` (both read by
+  `cluster:create` and `cluster:apply`). The host is resolved by name
+  (`helpers/virtual-cluster.ts`); no host = the shared cluster.
+  `cluster:apply` only creates a virtual cluster - nothing else to reconcile;
+  `validateDesired` rejects node settings on it and `host` without it.
+- `GraphqlClienAPI.provisionProjectVirtualCluster` selects `routerUrl` and
+  `hostNamespace` itself (not in `ClusterFragment`, so older servers keep
+  working). Canonical doc: `graphql-server-functions/docs/features/virtual-clusters.md`.
+- **Test:** `npx jest --coverage=false test/cluster-apply`.
+- **Debug:** `No cluster named "<host>"` = the host name is not a live
+  cluster of the project (`gcli cluster:list`).
+- **Verification:** jest 118/118 (4 new), tsc + eslint clean. README-CLI.md
+  not regenerated (needs a build of release/index.js).

package/docs/features/README.md

@@ -36,3 +36,4 @@ Outline (drop sections that don't apply):
 | `dedicated-platform-cluster` | [dedicated-platform-cluster.md](dedicated-platform-cluster.md) | `cluster:status/health/scale/autoscale/...` commands; canonical doc in lambforge-agent |
 | `ci-token-scopes` | [ci-token-scopes.md](ci-token-scopes.md) | Which permission each command needs; `mq-trigger:*` commands; canonical doc in graphql-server |
 | `workflows` | [workflows.md](workflows.md) | `workflow:*` commands incl. AI drafts (`workflow:generate`); canonical doc in graphql-server-lambdas |
+| `virtual-clusters` | [virtual-clusters.md](virtual-clusters.md) | cluster:create --virtual, provider: vcluster (slice; canonical in graphql-server-functions) |

package/docs/features/virtual-clusters.md

@@ -0,0 +1,12 @@
+# Virtual clusters (slice)
+
+**Status:** built and tested end to end on minikube 2026-10-28, not deployed. Feature slug `virtual-clusters`.
+Canonical doc (how it works, test, debug, limits):
+[`graphql-server-functions/docs/features/virtual-clusters.md`](../../../../../graphql-server-functions/docs/features/virtual-clusters.md).
+
+Virtual clusters are vClusters (own Kubernetes API + Fission) on the shared
+cluster or one of the project's private clusters, `provider: 'vcluster'`.
+
+## This repo
+
+`gcli cluster:create --virtual [--host <private-cluster>]`; in `lambforge.yaml`: `cluster: { name: dev, provider: vcluster, host: prod }` for `cluster:create` / `cluster:apply` (no host = shared cluster; node settings are rejected). Code: `src/commands/cluster/helpers/virtual-cluster.ts`, `helpers/plan.ts`. Test: `npx jest --coverage=false test/cluster-apply`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gapi/gcli",
-  "version": "1.8.247",
+  "version": "1.8.248",
   "repository": {
     "type": "git",
     "url": "https://github.com/Stradivario/gapi.git"