Setting the file. One moment.
Subchapter 27.86
references/vendored/clarify/clarify-multicloud.mdMarkdown4 KBView on GitHub
Canonical multi-cloud-portability question for Clarify’s Global/Strategic category, vendored into each skill that runs a full-migration Clarify phase () and kept byte-identical by . Whether a customer needs to keep running workloads across multiple cloud providers does not depend on which cloud they are migrating FROM, so the question and its early-exit consequence are identical everywhere.
references/vendored/clarify/clarify-multicloud.mdshared:syncgcp-to-aws has this as an early-exit strategic question (its Q5) that
immediately forces EKS and skips the Kubernetes-sentiment question entirely
when the answer is yes. azure-to-aws had no standalone equivalent — its
compute-target question (Q-C1) offers EKS as one of three options, described
only as “only if your team already runs Kubernetes,” with no dedicated
portability gate and no early-exit behavior. A customer with a genuine
multi-cloud requirement on Azure gets asked a plain compute-preference
question instead of having their hard constraint recognized up front.
Multi-cloud portability is an immediate decision point — if required, Kubernetes (EKS) is the only portable abstraction, and we can skip several compute questions.
- Yes, multi-cloud required
- No, AWS-only is acceptable
- I don’t know
| Answer | Recommendation Impact |
|---|---|
| Yes, multi-cloud required | Immediate EKS recommendation — Kubernetes is the only portable abstraction layer. Skip the Kubernetes-sentiment / compute-target question. Container-orchestration-eligible PaaS compute (Cloud Run, App Engine, App Service) routes to EKS too, overriding its normal default target. |
| No, AWS-only acceptable | Full compute decision tree continues — EKS vs the simpler managed-container option is evaluated based on team sentiment / detected signals |
1 -> compute: "eks" — Immediate EKS recommendation. EARLY EXIT: skip the compute-target / K8s-sentiment question.
2 -> (no constraint written — full compute decision tree continues)
3 -> same as default (2) — assume AWS-onlyDefault: 2 — no constraint, evaluate the full compute decision tree.