Get C_KYMD_01 Dumps : Verified SAP Certified Development Associate - Side-by-Side Extensibility based on SAP BTP, Kyma runtime

 The API Gateway in Kyma is a custom-configured Istio Ingress Gateway that is installed in the kyma-system namespace called kyma-gateway. Istio is an open-source project that provides a service mesh for microservices. It enables traffic management, security, observability, and policy enforcement for the services in the cluster. The API Gateway uses Istio resources to expose and secure APIs for the workloads in Kyma. References: Using the API Gateway to Expose Services, SAP BTP, Kyma Runtime API Gateway future architecture based on Istio, GitHub - kyma-project/api-gateway.

A pod object is a Kubernetes resource that represents a group of one or more containers that share storage and network resources, and a specification for how to run the containers. A pod object has the following parts:

• kind: This is the type of the resource, which is always Pod for pod objects.
• ap Version: This is the version of the API that the pod object uses, which is usually v1 for pod objects.
• metadata: This is a set of data that identifies and labels the pod object, such as name, namespace, labels, and annotations.

The other options are not parts of a pod object, but they are related to other Kubernetes concepts:

• etod: This is a misspelling of etcd, which is a key-value store that holds the cluster data, such as pod objects, but it is not part of the pod object itself.
• kubelet: This is an agent that runs on each node in the cluster and communicates with the control plane. The kubelet is responsible for creating, starting, and deleting pod objects on the node, but it is not part of the pod object itself.

References: Side-by-Side Extensibility Based on SAP BTP, Kyma Runtime - Unit 2 - Lesson 1: Kubernetes and Kyma Core Concepts, Kubernetes Documentation - Pods, Kubernetes Documentation - Kubernetes Objects.

To post events to Kyma Eventing using the Cloud Events specification, you need to use the service/eventing-event-publisher-proxy component. This component is responsible for validating and forwarding events to the Eventing Controller, which then dispatches them to the subscribers. The other components are not relevant for this purpose. The pod/eventing-event-publisher-proxy is the name of the pod that runs the service, but it is not the component that you use to post events. The pods/eventing-nats-0 and svc/eventing-nats are related to the NATS eventing framework, which is the default eventing backend in Kyma, but they are not the components that you use to post events using the Cloud Events specification. References: Side-by-Side Extensibility Based on SAP BTP, Kyma Runtime - Unit 4 - Lesson 1: Eventing in Kyma, Kyma Documentation - Event Publisher Proxy

 A CronJob is a workload type that creates Jobs on a repeating schedule, based on the Cron syntax. A Job is a workload type that runs a task to completion, just once. A Deployment is a workload type that manages a set of Pods that are created from the same template. A StatefulSet is a workload type that manages a set of Pods that have stable identities and persistent storage. References: CronJob, Jobs, Workloads.

A service manifest is a YAML file that defines a service, which is a Kubernetes resource that groups a set of pods and provides a way to access them within a cluster1. A service manifest must have the following mandatory metrics2:

• Kind: The kind of the resource, which must be Service for a service manifest.
• Type: The type of the service, which determines how the service is exposed. The possible values are ClusterIP, NodePort, LoadBalancer, or ExternalName3.
• Ports: The list of ports that the service exposes. Each port must have a name, a protocol, and a port number.

References:

• 1: Kubernetes / Services
• 2: Kubernetes / Service - v1 core
• 3: Kubernetes / Publishing Services (ServiceTypes)