On-call staff propose a runbook that SSHes to node-3 and pip installs the DNA dashboard wherever capacity appears. How should Docker and Kubernetes CD integration work instead?
Select an answer to reveal the explanation.
Short Explanation
One sealed meal kit, any kitchen with an open burner—Kubernetes schedules the same image wherever capacity exists. SSH pip install on node-3 is a snowflake, not CD integration.
Full Explanation
Docker and Kubernetes CD integration schedules the same container image onto whichever node has capacity. A runbook that SSHes and pip installs on a specific node is not that model. Underlay switching topics and permanent host binding miss the schedulable-image skill under test.