This sample deployment pulls a container imageįrom a public repository and deploys three replicas (individual Pods) of it to yourĬluster. Your VPC must also have at least one private subnet.Ĭreate a Kubernetes deployment. Profile created in the getting started guides doesn't specify the namespace used in If you used one of the getting started guides to create your cluster, then you'll have toĬreate a new profile, or add the namespace to your existing profile, because the Same namespace created in this tutorial, which is eks-sample-app, If you plan to deploy your sample workload to Fargate, then you must have anĮxisting Fargate profile that includes the Information, see Creating or updating a kubeconfig file for an Amazon EKS cluster. Kubectl configured to communicate with your cluster. For more information, see Installing or updating kubectl. Windows application, then you must have Windows support enabled for yourĬluster and at least one Amazon EC2 Windows node. If you don't have an existingĪmazon EKS cluster, you can deploy one using one of the Getting started with Amazon EKS guides. Further details can be found in the Service Configuration #admission-controller-filtering-settings documentation.įor more details surrounding gang-scheduling labels and annotations, please refer to the documentation on gang scheduling.An existing Kubernetes cluster with at least one node. Further details can be found in the Service Configuration #admission-controller-filtering-settingsdocumentation.Ĭontrols which namespaces will have pods labeled with an applicationId. Replaced with namespace.quota since version 1.2.0Ĭontrols which namespaces will have pods forwarded to Yunikorn for scheduling. Further details can be found in the Resource Quota Management documentation. Set the maximum capacity of the queue mapped to this namespace. Further details can be found in the DaemonSet Scheduling using Simple Preemptor documentation.ĭefine a parent queue for a set of K8s namespaces. It will trigger opt out of preemption for pods with that specific priority class. The allow-preemption annotation can only be set on the Priorit圜lass object. Each pod within an application must define all task groups.Īrbitrary key-value pairs used to customize scheduling policies such as gang scheduling. It must be listed within task-groups.ĭefines the set of task groups for this application for gang scheduling. Sets the task group name this pod belongs to for the purposes of gang scheduling. The priority of queue is determined by: label queue > annotation /queue > default. Selects the YuniKorn queue this application should be scheduled in. ![]() The priority of applicationID is determined by: annotation /app-id > label applicationId > label SparkLabelAppID. Set internally by YuniKorn.Īll annotations are under the namespace. Set if this pod represents a placeholder for gang scheduling. Set internally by the YuniKorn admission controller. If present, disables the YuniKorn state-aware scheduling policy for this pod. This may be ignored if a placement policy is in effect.Īlternative method of specifying applicationId used by Spark Operator if the label applicationId and annotation /app-id unset. YuniKorn utilizes several Kubernetes labels and annotations to support various features: Labels in YuniKorn Name Labels and Annotations in YuniKorn Labels and Annotations in YuniKorn
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |