OPS-001: Kubernetes Deployment Manifests #152
Labels
No labels
blocked:children
blocked:commit-ready-failed
blocked:depends-231
blocked:depends-236
blocked:depends-237
blocked:depends-238
blocked:depends-239
blocked:gate-fetch
blocked:gate-fetch
blocked:gate-lint
blocked:gate-research
blocked:needs-attention
blocked:needs-decision
blocked:no-changes
blocked:no-procedure
blocked:preflight
blocked:verify-failed
bug
enhancement
feature-request
high-priority
in-progress
lint-cleanup
needs-decompose
needs-triage
ops-retry
ops-task
phase-5
quickfix
security/medium
self-building
triage-approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/mesh-seed#152
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Required
Acceptance Criteria
Ops Pipeline — Not an Ops Task
This issue was labeled
ops-taskbut 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
Landed via PR #279 — OPS-001 Kubernetes Deployment Manifests now on origin/master.
6a8f6a5(merge offix/mesh-seed-152-land-k8s-manifests, branch base commitca97178)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.