Issues

The lab registers its own cluster as the infrastructure families (kubernetes, prometheus; capi with #56) the way an installation does — the Infrastructure preset resolves to x_kubernetes_/x_prometheus_ with management_cluster=agentlab, and the fake fleet retires

#168

· teemow opened

on Sep 12, 2026

proofs: a tenant step — a person RBAC denies gets an empty roster and no session through the edge, the same answer as the Dev Portal

#166

· teemow opened

on Sep 12, 2026

fix(config): a missing platform.valuesFiles entry is reported as 'no agentlab.yaml found', and blocks down

#165

· teemow opened

on Sep 12, 2026

agentlab open prometheus: route the lab Prometheus under its own prefix so its web UI works, then add the `open` target

enhancement

#151

· marians opened

on Sep 11, 2026

Side-loaded images are imported as unprefixed import-<date>@sha256 refs; after a container restart kubelet's checkpoint-image check fails with CreateContainerError until the ref is removed on the node

#150

· teemow opened

on Sep 11, 2026

platform.chartPath labs set kagent.serviceMonitor.enabled: true, so platform-test expects a kagent scrape the kagent line never serves

#149

· teemow opened

on Sep 11, 2026

GPU proof on the lab-created cloud cluster (after #56/#57): Add GPU node pool → serving slice → LLMInferenceService → the model endpoint with and without a token → an agent turn → teardown with the cluster proves the pool's deletion; apply mode, no mock (bumblebee-plans#46 D10 proof 2)

#128

· teemow opened

on Sep 9, 2026

Docs follow the end-user CLI: up as the first command, open/list/pods as the everyday ones, the command reference grouped like --help, kubectl optional

documentation

enhancement

#127

· teemow opened

on Sep 9, 2026

First run: without an agentlab.yaml, configure and up ask one question — use the detected defaults or customize? — and only Customize runs the form

enhancement

#125

· teemow opened

on Sep 9, 2026

agentlab pods: the lab's pods across namespaces through the embedded client, kubectl get pods -A shaped, with a namespace filter

enhancement

#122

· teemow opened

on Sep 9, 2026

agentlab list: every lab on this machine — name, directory, cluster state, components, URLs, whether the lab CA is trusted

enhancement

#121

· teemow opened

on Sep 9, 2026

A registry of labs: --lab on every command, the one lab as the default, a picker among several (an agentlab.yaml in the current directory still wins)

enhancement

#120

· teemow opened

on Sep 9, 2026

Navigation Menu

Uh oh!

All issues

The lab registers its own cluster as the infrastructure families (kubernetes, prometheus; capi with #56) the way an installation does — the Infrastructure preset resolves to x_kubernetes_/x_prometheus_ with management_cluster=agentlab, and the fake fleet retires

proofs: a tenant step — a person RBAC denies gets an empty roster and no session through the edge, the same answer as the Dev Portal

fix(config): a missing platform.valuesFiles entry is reported as 'no agentlab.yaml found', and blocks down

agentlab open prometheus: route the lab Prometheus under its own prefix so its web UI works, then add the `open` target

Side-loaded images are imported as unprefixed import-<date>@sha256 refs; after a container restart kubelet's checkpoint-image check fails with CreateContainerError until the ref is removed on the node

platform.chartPath labs set kagent.serviceMonitor.enabled: true, so platform-test expects a kagent scrape the kagent line never serves

GPU proof on the lab-created cloud cluster (after #56/#57): Add GPU node pool → serving slice → LLMInferenceService → the model endpoint with and without a token → an agent turn → teardown with the cluster proves the pool's deletion; apply mode, no mock (bumblebee-plans#46 D10 proof 2)

Docs follow the end-user CLI: up as the first command, open/list/pods as the everyday ones, the command reference grouped like --help, kubectl optional

First run: without an agentlab.yaml, configure and up ask one question — use the detected defaults or customize? — and only Customize runs the form

agentlab pods: the lab's pods across namespaces through the embedded client, kubectl get pods -A shaped, with a namespace filter

agentlab list: every lab on this machine — name, directory, cluster state, components, URLs, whether the lab CA is trusted

A registry of labs: --lab on every command, the one lab as the default, a picker among several (an agentlab.yaml in the current directory still wins)

Uh oh!

Search results