OPS-001: Kubernetes Deployment Manifests #152

Closed
opened 2026-04-11 05:49:49 +00:00 by Mark · 2 comments
Owner

Required

  • Deployments for all services
  • Services and Ingress
  • ConfigMaps and Secrets
  • Helm chart optional

Acceptance Criteria

  • All components deployable to K8s
  • Horizontal scaling works
  • Health checks configured
  • Resource limits set
## Required - Deployments for all services - Services and Ingress - ConfigMaps and Secrets - Helm chart optional ## Acceptance Criteria - [ ] All components deployable to K8s - [ ] Horizontal scaling works - [ ] Health checks configured - [ ] Resource limits set
Author
Owner

Ops Pipeline — Not an Ops Task

This issue was labeled ops-task but doesn't appear to be an operations task. It has been returned to feature triage for proper routing.

Research analysis:
IS_OPS: NO
HOST: localhost
STATUS: NOT_OPS
EVIDENCE: Creating Kubernetes Deployment Manifests is writing YAML configuration files — infrastructure-as-code authoring. This involves design decisions (service architecture, scaling policies, health check endpoints, resource allocation, ingress routing) which are architecture/design work, not operational execution. No actual deployment, server interaction, API calls, or infra changes are being performed. The task is producing code/config to be committed to a repository, which is feature/design work. The ops part would be applying those manifests to a cluster (kubectl apply), which is not asked for here. Additionally, the repository "mesh-seed" does not exist on this host or in Forgejo, so even if it were an ops task the context is missing.

PROCEDURE: N/A — not an ops task. Would require checking the mesh-seed project structure, identifying services, and writing deployment YAMLs as code work.

VERIFY: N/A

RISKS: N/A

## Ops Pipeline — Not an Ops Task This issue was labeled `ops-task` but doesn't appear to be an operations task. It has been returned to feature triage for proper routing. **Research analysis:** IS_OPS: NO HOST: localhost STATUS: NOT_OPS EVIDENCE: Creating Kubernetes Deployment Manifests is writing YAML configuration files — infrastructure-as-code authoring. This involves design decisions (service architecture, scaling policies, health check endpoints, resource allocation, ingress routing) which are architecture/design work, not operational execution. No actual deployment, server interaction, API calls, or infra changes are being performed. The task is producing code/config to be committed to a repository, which is feature/design work. The ops part would be applying those manifests to a cluster (kubectl apply), which is not asked for here. Additionally, the repository "mesh-seed" does not exist on this host or in Forgejo, so even if it were an ops task the context is missing. PROCEDURE: N/A — not an ops task. Would require checking the mesh-seed project structure, identifying services, and writing deployment YAMLs as code work. VERIFY: N/A RISKS: N/A
Mark closed this issue 2026-07-27 00:30:42 +00:00
Author
Owner

Landed via PR #279 — OPS-001 Kubernetes Deployment Manifests now on origin/master.

  • Merge commit: 6a8f6a5 (merge of fix/mesh-seed-152-land-k8s-manifests, branch base commit ca97178)
  • PR: #279
  • Contents: 9 raw k8s manifests + kustomization.yaml + apply.sh + README.md (k8s/), 9 Helm templates (helm/mesh-seed/templates/), values.yaml parity
  • All 474cb6e files verified byte-identical on origin/master.

Acceptance criteria met: 5 Deployments (gateway, mesh-node, worker, prometheus, grafana) + 1 StatefulSet (redis), 5 Services + 1 Ingress, ConfigMap + Secret, HPA on worker, liveness/readiness probes, resource limits. ruff clean, tests/unit/test_deployment_manager.py 17/17, helm template renders 31 resources.

**Landed via PR #279** — OPS-001 Kubernetes Deployment Manifests now on origin/master. - Merge commit: `6a8f6a5` (merge of `fix/mesh-seed-152-land-k8s-manifests`, branch base commit `ca97178`) - PR: https://forgejo.tail018ac4.ts.net/Mark/mesh-seed/pulls/279 - Contents: 9 raw k8s manifests + kustomization.yaml + apply.sh + README.md (k8s/), 9 Helm templates (helm/mesh-seed/templates/), values.yaml parity - All 474cb6e files verified byte-identical on origin/master. Acceptance criteria met: 5 Deployments (gateway, mesh-node, worker, prometheus, grafana) + 1 StatefulSet (redis), 5 Services + 1 Ingress, ConfigMap + Secret, HPA on worker, liveness/readiness probes, resource limits. ruff clean, tests/unit/test_deployment_manager.py 17/17, helm template renders 31 resources.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Mark/mesh-seed#152
No description provided.