{"id":"bare-metal-edge-requires-full-stack-specialization","text":"Bare metal edge deployments require specialized infrastructure at every layer AND fleet-scale lifecycle management: provisioning uses BMC+Ironic+MetalLB (not cloud APIs), while ZTP+TALM handle provisioning and updates at scale with canary failure gating — making bare metal edge the most infrastructure-demanding deployment topology.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["bare-metal-requires-specialized-infra-at-every-layer","edge-fleet-management-pipeline"],"outlist":[],"label":"depth-2 bare metal infra + depth-2 edge fleet management combine into the most operationally complex deployment model"}],"dependents":["bare-metal-edge-maximum-divergence-from-platform-model"],"metadata":{},"explanation":{"steps":[{"node":"bare-metal-edge-requires-full-stack-specialization","truth_value":"IN","reason":"SL justification valid","antecedents":["bare-metal-requires-specialized-infra-at-every-layer","edge-fleet-management-pipeline"],"label":"depth-2 bare metal infra + depth-2 edge fleet management combine into the most operationally complex deployment model"},{"node":"bare-metal-requires-specialized-infra-at-every-layer","truth_value":"IN","reason":"SL justification valid","antecedents":["bare-metal-provisioning-architecture","metallb-bare-metal-networking-model"],"label":"depth-2 — bare metal demands explicit infrastructure at provisioning and networking layers that cloud platforms abstract away"},{"node":"bare-metal-provisioning-architecture","truth_value":"IN","reason":"SL justification valid","antecedents":["bare-metal-ipi-uses-bmc","bmh-rootdevicehints-model-vendor-substring","provisioning-consumed-by-cluster-baremetal-operator","provisioning-ip-inside-subnet-outside-dhcp"],"label":"Full bare metal provisioning stack from BMC through metal3"},{"node":"bare-metal-ipi-uses-bmc","truth_value":"IN","reason":"premise"},{"node":"bmh-rootdevicehints-model-vendor-substring","truth_value":"IN","reason":"premise"},{"node":"provisioning-consumed-by-cluster-baremetal-operator","truth_value":"IN","reason":"premise"},{"node":"provisioning-ip-inside-subnet-outside-dhcp","truth_value":"IN","reason":"premise"},{"node":"metallb-bare-metal-networking-model","truth_value":"IN","reason":"SL justification valid","antecedents":["metallb-l2-failover-gratuitous-arp","metallb-bgp-single-asn-requirement"],"label":"MetalLB L2 and BGP modes form the bare metal external networking model"},{"node":"metallb-l2-failover-gratuitous-arp","truth_value":"IN","reason":"premise"},{"node":"metallb-bgp-single-asn-requirement","truth_value":"IN","reason":"premise"},{"node":"edge-fleet-management-pipeline","truth_value":"IN","reason":"SL justification valid","antecedents":["ztp-pattern-edge-fleet-management","talm-canary-failure-stops-update","sno-reduced-capability-profile","vdu-firmware-cstates-c0-c1-only"],"label":"ZTP provisioning, TALM updates, SNO topology, and vDU constraints form a complete edge lifecycle"},{"node":"ztp-pattern-edge-fleet-management","truth_value":"IN","reason":"premise"},{"node":"talm-canary-failure-stops-update","truth_value":"IN","reason":"premise"},{"node":"sno-reduced-capability-profile","truth_value":"IN","reason":"SL justification valid","antecedents":["ocpvirt-sno-no-live-migration-ha","sriov-sno-disable-drain","sno-worker-requires-ocp-411"],"label":"SNO trades operational features for minimal footprint"},{"node":"ocpvirt-sno-no-live-migration-ha","truth_value":"IN","reason":"premise"},{"node":"sriov-sno-disable-drain","truth_value":"IN","reason":"premise"},{"node":"sno-worker-requires-ocp-411","truth_value":"IN","reason":"premise"},{"node":"vdu-firmware-cstates-c0-c1-only","truth_value":"IN","reason":"premise"}]}}