1V0-71.21 · Question #32
What three open source projects are included in Tanzu Kubernetes Grid? (Choose three.)
The correct answer is A. Contour D. Harbor F. Velero. Tanzu Kubernetes Grid (TKG) bundles Contour (ingress controller), Harbor (container image registry), and Velero (cluster backup/restore) as core open source components because they address the three foundational operational needs of any production Kubernetes platform: traffic…
Question
What three open source projects are included in Tanzu Kubernetes Grid? (Choose three.)
Options
- AContour
- BVitess
- CAnsible
- DHarbor
- ECrossplane
- FVelero
How the community answered
(31 responses)- A94% (29)
- B3% (1)
- C3% (1)
Explanation
Tanzu Kubernetes Grid (TKG) bundles Contour (ingress controller), Harbor (container image registry), and Velero (cluster backup/restore) as core open source components because they address the three foundational operational needs of any production Kubernetes platform: traffic routing, image management, and disaster recovery.
Vitess (B) is a MySQL clustering solution - database infrastructure unrelated to TKG's scope. Ansible (C) is a Red Hat configuration management tool that VMware doesn't bundle into TKG. Crossplane (E) is a control-plane extension for infrastructure provisioning that is not part of the TKG package.
Memory tip: Think of a ship at sea - a Contour map guides it into the Harbor, where cargo is secured with Velero (velcro). Ingress → Registry → Backup. The three wrong answers (Vitess, Ansible, Crossplane) all belong to different ecosystems (databases, automation, multi-cloud) that TKG doesn't own.
Topics
Community Discussion
6
Carlos M.Mar 13, 2026A, D, F is right. Tanzu Kubernetes Grid bundles Contour (ingress controller), Harbor (container image registry), and Velero (cluster backup and restore) as its included open source projects, while the others like Vitess, Ansible, and Crossplane are not part of the TKG stack.
Ola B.Mar 5, 2026I picked Crossplane first, but spinning up TKG confirmed Contour, Harbor, Velero.
Oszkar V.Mar 18, 2026I keep seeing people overlook C on this one and I think that is a mistake. TKG leans heavily on Ansible under the hood for node provisioning and cluster lifecycle automation, and if you have spent any time watching SDDC Manager hand off cluster build tasks you can see that Ansible-based playbooks are doing real work in that pipeline, not just as an optional add-on but as a core dependency VMware ships with the bundle.
Ola B.Mar 20, 2026Oszkar, you are right that Ansible shows up in the broader VCF pipeline, but the exam is asking specifically about what TKG itself ships with for cluster lifecycle management, and if you spin up a TKG lab you will see it leans on Cluster API, Pinniped, and Contour as core bundled components, which maps to A, D, and F, not the Ansible dependency that lives more on the SDDC Manager side of the house.
Lena V.Mar 24, 2026Contour, Harbor, Velero ship with TKG, but do you know what role each fills?
Carlos M.Mar 26, 2026Contour handles ingress (Layer 7 HTTP routing), Harbor is your private container registry, and Velero takes care of cluster backup and disaster recovery, so together they cover the networking, artifact storage, and data protection gaps that vanilla Kubernetes leaves open.