{"id":"hcp-requires-distinct-operational-playbook","text":"Hosted control planes require a fundamentally different operational playbook from standalone clusters: machine management uses NodePool instead of MachineSet/MHC, ClusterVersion is ignored in favor of HostedCluster CR for updates, the web console cannot show control plane status or manage machines, and etcd restore uses a restart-date annotation — making standalone operational procedures largely inapplicable.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["hcp-diverges-from-standalone-machine-and-provisioning","hcp-clusterversion-ignored","hcp-web-console-limitations","hcp-force-rollout-restart-date-annotation"],"outlist":[],"label":"Each HCP divergence point invalidates a standalone operational procedure — together they demonstrate that HCP needs its own runbook, not adaptations of standalone procedures"}],"dependents":["alternative-topologies-diverge-from-standard-operations"],"metadata":{},"explanation":{"steps":[{"node":"hcp-requires-distinct-operational-playbook","truth_value":"IN","reason":"SL justification valid","antecedents":["hcp-diverges-from-standalone-machine-and-provisioning","hcp-clusterversion-ignored","hcp-web-console-limitations","hcp-force-rollout-restart-date-annotation"],"label":"Each HCP divergence point invalidates a standalone operational procedure — together they demonstrate that HCP needs its own runbook, not adaptations of standalone procedures"},{"node":"hcp-diverges-from-standalone-machine-and-provisioning","truth_value":"IN","reason":"SL justification valid","antecedents":["hcp-differs-from-standalone-in-machine-management","bare-metal-provisioning-architecture"],"label":"Machine lifecycle management is architecturally split between HCP and standalone patterns"},{"node":"hcp-differs-from-standalone-in-machine-management","truth_value":"IN","reason":"SL justification valid","antecedents":["hcp-nodepool-autorepair-spec","hcp-nodepool-upgrade-types-replace-inplace","hcp-nodepool-spec-config-vs-tuningconfig","hcp-managed-via-hypershift-operator"],"label":"HCP centralizes machine lifecycle into the NodePool abstraction"},{"node":"hcp-nodepool-autorepair-spec","truth_value":"IN","reason":"premise"},{"node":"hcp-nodepool-upgrade-types-replace-inplace","truth_value":"IN","reason":"premise"},{"node":"hcp-nodepool-spec-config-vs-tuningconfig","truth_value":"IN","reason":"premise"},{"node":"hcp-managed-via-hypershift-operator","truth_value":"IN","reason":"premise"},{"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":"hcp-clusterversion-ignored","truth_value":"IN","reason":"premise"},{"node":"hcp-web-console-limitations","truth_value":"IN","reason":"premise"},{"node":"hcp-force-rollout-restart-date-annotation","truth_value":"IN","reason":"premise"}]}}