Air-Gapped Expectation Setting
Situation
The customer expects a deployment or POC in an air-gapped environment to move at the same speed as an internet-connected environment.
What the customer may say
"It's air-gapped, but installation should be standard."
What you should say
"Air-gapped work is doable, but it changes the delivery plan. We need to account for artifact transfer, dependency mirroring, access windows, validation steps, and the customer-owned approval path."
What not to say
"Air-gapped should not change much."
Follow-up question
"What is the approved process for moving images, packages, logs, and troubleshooting artifacts into and out of the environment?"