Fixit card t_550b5668 did not resolve #152 — no K8s deployment manifests landed #254

New issue

Closed

opened 2026-07-22 18:25:25 +00:00 by Mark · 1 comment

Mark commented

2026-07-22 18:25:25 +00:00

Owner

Finding from post-deploy probe of mesh-seed #152

Description

The fixit card t_550b5668 claimed to have resolved issue #152 (OPS-001: Kubernetes Deployment Manifests). However, a post-deploy probe found no evidence that a fix actually landed:

Issue #152 is still OPEN — state: open, closed_at: null, last updated 2026-07-15
No fix commit references #152 in git history
No PR references #152 — only PR #242 (SLO specs for #150) was merged
Existing K8s assets are incomplete: k8s/operator-deployment.yaml, crds.yaml, rbac.yaml, and helm/ exist but are missing:
- No Service manifest
- No Ingress manifest
- No ConfigMaps
- No Secrets
- No health probes / readiness checks
- No HorizontalPodAutoscaler (HPA)

Expected

The fixit card should have delivered the Kubernetes manifests specified in #152's acceptance criteria:

Deployments for all services
Services and Ingress
ConfigMaps and Secrets
Health checks configured
Resource limits set

Actual

No K8s deployment deliverables were found. Issue #152 remains unaddressed.

Suggested action

Investigate what fixit card t_550b5668 actually resolved (it may have addressed a different scope entirely). Re-triage #152 for the OPS-001 Kubernetes Deployment scope.

References

Original issue: Mark/mesh-seed#152
Kanban card: t_43217562 (QA board — post-deploy probe)

## Finding from post-deploy probe of mesh-seed #152 ### Description The fixit card `t_550b5668` claimed to have resolved issue #152 (OPS-001: Kubernetes Deployment Manifests). However, a post-deploy probe found **no evidence that a fix actually landed**: - **Issue #152 is still OPEN** — state: `open`, closed_at: `null`, last updated 2026-07-15 - **No fix commit references #152** in git history - **No PR references #152** — only PR #242 (SLO specs for #150) was merged - **Existing K8s assets are incomplete**: `k8s/operator-deployment.yaml`, `crds.yaml`, `rbac.yaml`, and `helm/` exist but are **missing**: - No `Service` manifest - No `Ingress` manifest - No `ConfigMaps` - No `Secrets` - No health probes / readiness checks - No `HorizontalPodAutoscaler` (HPA) ### Expected The fixit card should have delivered the Kubernetes manifests specified in #152's acceptance criteria: - Deployments for all services - Services and Ingress - ConfigMaps and Secrets - Health checks configured - Resource limits set ### Actual No K8s deployment deliverables were found. Issue #152 remains unaddressed. ### Suggested action Investigate what fixit card `t_550b5668` actually resolved (it may have addressed a different scope entirely). Re-triage #152 for the OPS-001 Kubernetes Deployment scope. ### References - Original issue: Mark/mesh-seed#152 - Kanban card: `t_43217562` (QA board — post-deploy probe)

Mark added the

bug

label

2026-07-22 18:25:25 +00:00

Mark added the

triage-approved

label

2026-07-26 14:47:12 +00:00

Mark added the

blocked:preflight

label

2026-07-31 04:26:40 +00:00

Mark commented

2026-08-01 17:40:17 +00:00

Author

Owner

QA verification complete (kanban card t_a22b0ddf).

Summary:

Issue #152 is now closed on Forgejo.
The fixit card t_550b5668 produced the missing K8s/Helm manifests, but they landed as an untracked-files stash (474cb6e) and were never committed/pushed to origin/master.
The stashed manifests satisfy all #152 acceptance criteria (Deployments, Services, Ingress, Secrets, ConfigMaps, HPA, health checks, resource limits).
Closing this probe as verified; the remaining work is to land the stashed manifests on master.

QA verification complete (kanban card t_a22b0ddf). Summary: - Issue #152 is now closed on Forgejo. - The fixit card t_550b5668 produced the missing K8s/Helm manifests, but they landed as an untracked-files stash (474cb6e) and were never committed/pushed to origin/master. - The stashed manifests satisfy all #152 acceptance criteria (Deployments, Services, Ingress, Secrets, ConfigMaps, HPA, health checks, resource limits). - Closing this probe as verified; the remaining work is to land the stashed manifests on master.

Mark closed this issue

2026-08-01 17:40:24 +00:00

Mark removed the

blocked:preflight

label

2026-08-14 05:41:52 +00:00

Mark referenced this issue

2026-09-18 17:56:41 +00:00

[Mark/mesh-seed #231] Remove stale blocked:preflight label from closed issue #278