VMware Updated 2V0-71.23 Exam Questions and Answers by drew

To visualize API connectivity and enable API protection in VMware Tanzu Service Mesh, the administrator needs to perform two steps:

• Activate API Discovery for the Global Namespace. This allows Tanzu Service Mesh to automatically discover the APIs signatures between microservices running inside or outside the mesh. API Discovery creates a custom API schema for each API that is close to OpenAPI spec 3.0. Tanzu Service Mesh graph renders the detected APIs in the Enforcing mode by default, which means that any new API is considered as a violated API unless accepted by the administrator1
• Create API Security Policy for the Global Namespace. This allows the administrator to block or allow layer 4 and layer 7 traffic, as well as create granular policies that provide API and data segmentation, OWASP 10 attack defense, schema validation, geofencing, data compliance, and egress controls. The administrator can create the API Security policy through the Tanzu Service Mesh Console UI or by using the Tanzu Service Mesh API Explorer2

References: 1: https://docs.vmware.com/en/VMware-Tanzu-Service-Mesh/services/tanzu-service-mesh-enterprise/GUID-E6FB9FB3-FDB3-4D2B-B5CB-614608EEF537.html  2: https://docs.vmware.com/en/VMware-Tanzu-Service-Mesh/services/tanzu-service-mesh-enterprise/GUID-5B635420-3BD2-4EC1-B67E-2015F991A91C.html

Two package management tools that can be used to configure and install applications on Kubernetes are:

• Carvel. Carvel is a set of tools that provides a simple, composable, and flexible way to manage Kubernetes configuration, packaging, and deployment. Carvel includes tools such as kapp, which applies and tracks Kubernetes resources in a cluster; ytt, which allows templating YAML files; kbld, which builds and pushes images to registries; kpack, which automates image builds from source code; and vendir, which syncs files from different sources into a single directory. Carvel is integrated with VMware Tanzu Kubernetes Grid and can be used to deploy and manage applications on Tanzu clusters.
• Helm. Helm is a tool that helps users define, install, and upgrade complex Kubernetes applications using charts. Charts are packages of pre-configured Kubernetes resources that can be customized with values. Helm uses a client-server architecture with a command line tool called helm and an in-cluster component called Tiller. Helm can be used to deploy applications from the official Helm charts repository or from custom charts created by users or vendors. Helm is also integrated with VMware Tanzu Kubernetes Grid and can be used to deploy and manage applications on Tanzu clusters.

References: : https://carvel.dev/ : https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid/1.6/vmware-tanzu-kubernetes-grid-16/GUID-tkg-carvel.html : https://helm.sh/ : https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid/1.6/vmware-tanzu-kubernetes-grid-16/GUID-tkg-helm.html

The role of the Tanzu Kubernetes Grid Service is to provision Kubernetes clusters that integrate with the underlying vSphere Namespace resources and Supervisor Services. The Tanzu Kubernetes Grid Service is a component of vSphere with Tanzu that provides self-service lifecycle management of Tanzu Kubernetes clusters3. A Tanzu Kubernetes cluster is an opinionated installation of Kubernetes that runs on top of the Supervisor Cluster and inherits its capabilities, such as storage integration, pod networking, load balancing, authentication, and authorization4. The Tanzu Kubernetes Grid Service exposes three layers of controllers to manage the lifecycle of a Tanzu Kubernetes cluster: Cluster API, Virtual Machine Service, and Tanzu Kubernetes Release Service3. References: Tanzu Kubernetes Grid Service Architecture - VMware Docs, What Is a Tanzu Kubernetes Cluster? - VMware Docs

Cluster API is a Kubernetes project that provides declarative APIs for cluster creation, configuration, and management. Cluster API uses a set of custom resource definitions (CRDs) to represent clusters, machines, and other objects. Cluster API also relies on providers to implement the logic for interacting with different infrastructure platforms. VMware Tanzu Kubernetes Grid uses Cluster API to deploy and manage Kubernetes clusters on various platforms. The three Cluster API providers being used in VMware Tanzu Kubernetes Grid are:

• CAPZ: Cluster API Provider for Azure. This provider enables Cluster API to create Kubernetes clusters on Microsoft Azure4.
• CAPV: Cluster API Provider for vSphere. This provider enables Cluster API to create Kubernetes clusters on vSphere 6.7 or later5.
• CAPA: Cluster API Provider for AWS. This provider enables Cluster API to create Kubernetes clusters on Amazon Web Services5.

References: VMware Tanzu Kubernetes Grid Documentation, Taking Kubernetes to the People: How Cluster API Promotes Self … - VMware