{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T22:44:07.049Z",
  "record_id": "VXI-EXT-PROCUREMENT-KUBERNETES-JOB-REPLACEMENT-01-v1",
  "record_kind": "external_reference",
  "title": "Kubernetes Jobs: Overlap during worker replacement",
  "system": "Kubernetes",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a Kubernetes Job parallelism setting prevent replacement workers overlapping terminating Pods?",
  "near_questions": [
    "Can Job Pods overlap while one is terminating?",
    "Does parallelism=1 guarantee one live worker during replacement?",
    "What does podReplacementPolicy Failed change?",
    "Can two Pods run for the same Job index?",
    "Which worker replaced the terminating Pod?",
    "Was TerminatingOrFailed configured?",
    "When did the old Pod actually reach Failed?",
    "Can replacement start before graceful shutdown finishes?",
    "Which effects occurred during Job replacement overlap?",
    "Does waiting for Pod failure guarantee once-only execution?",
    "What evidence checks a Kubernetes worker handover?",
    "Can INDEX inspect running Kubernetes Jobs?"
  ],
  "supported_claims": [
    {
      "claim": "The Kubernetes v1.34 documentation explains that replacement on TerminatingOrFailed can start a new Pod while the old one is still terminating, temporarily exceeding parallelism and allowing two Pods for one indexed task. The Failed replacement policy waits for terminal failure. This controls replacement timing; it does not prove external effects occur only once.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Exactly-once effects, external fencing or verification of the deployed cluster",
    "Verified buyer configuration, effective access or actual event completeness",
    "Runtime enforcement, certification or approval to act"
  ],
  "public_summary": "The Kubernetes v1.34 documentation explains that replacement on TerminatingOrFailed can start a new Pod while the old one is still terminating, temporarily exceeding parallelism and allowing two Pods for one indexed task. The Failed replacement policy waits for terminal failure. This controls replacement timing; it does not prove external effects occur only once.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Kubernetes: Pod replacement policy for Jobs",
    "source_url": "https://kubernetes.io/blog/2025/09/05/kubernetes-v1-34-pod-replacement-policy-for-jobs-goes-ga/",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-KUBERNETES-JOB-REPLACEMENT-01-v1",
    "candidate_record_sha256": "abd9e57deefad2739d4ad979ad3081d3e51da06a8a866a5c6098b5f48fb18a04",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "The Kubernetes v1.34 documentation explains that replacement on TerminatingOrFailed can start a new Pod while the old one is still terminating, temporarily exceeding parallelism and allowing two Pods for one indexed task. The Failed replacement policy waits for terminal failure. This controls replacement timing; it does not prove external effects occur only once.",
    "required_buyer_context": "Cluster version, Job replacement policy, parallelism and completion mode. Old and replacement Pod identifiers, index values and termination timelines. Worker outputs and external-effect reconciliation during the overlap period. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-17",
    "claim_to_check": "Does a Kubernetes Job parallelism setting prevent replacement workers overlapping terminating Pods?",
    "documented_statement": {
      "status": "documented",
      "statement": "The Kubernetes v1.34 documentation explains that replacement on TerminatingOrFailed can start a new Pod while the old one is still terminating, temporarily exceeding parallelism and allowing two Pods for one indexed task. The Failed replacement policy waits for terminal failure. This controls replacement timing; it does not prove external effects occur only once.",
      "source_ids": [
        "k8s-replace"
      ]
    },
    "buyer_evidence_required": [
      "Cluster version, Job replacement policy, parallelism and completion mode.",
      "Old and replacement Pod identifiers, index values and termination timelines.",
      "Worker outputs and external-effect reconciliation during the overlap period."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Decline exclusive-worker claims from parallelism alone without the replacement policy and Pod lifecycle evidence."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "k8s-replace",
        "url": "https://kubernetes.io/blog/2025/09/05/kubernetes-v1-34-pod-replacement-policy-for-jobs-goes-ga/",
        "final_url": "https://kubernetes.io/blog/2025/09/05/kubernetes-v1-34-pod-replacement-policy-for-jobs-goes-ga/",
        "title": "Kubernetes: Pod replacement policy for Jobs",
        "checked_on": "2026-10-17",
        "captured_at_utc": "2026-10-17T22:37:23.905Z",
        "version_context": "Kubernetes v1.34 feature announcement dated 2025-09-05",
        "sha256": "ab281709b68d68bd210f200fee9ff7880ebc7b47c9369b625886e77e58438d41",
        "bytes": 496761,
        "hash_basis": "Decoded HTTP response body bytes; not a signature or truth guarantee",
        "reviewed_sections": [
          "Why do we need pod replacement policy?; Example"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "Recovery can run overlapping workers even when the declared parallelism appears to allow only one.",
      "free": "Complete review, practical questions, sources and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Cluster version, Job replacement policy, parallelism and completion mode. Old and replacement Pod identifiers, index values and termination timelines. Worker outputs and external-effect reconciliation during the overlap period."
    },
    "buyer_relevance": "Recovery can run overlapping workers even when the declared parallelism appears to allow only one.",
    "refusal_conditions": [
      "Decline exclusive-worker claims from parallelism alone without the replacement policy and Pod lifecycle evidence."
    ]
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#kubernetes-job-replacement-terminating-pod-overlap",
  "machine_readable_record": "/varexis-index/records/kubernetes-job-replacement-terminating-pod-overlap.json"
}
