{"type":"doc","content":[{"type":"paragraph","content":[{"text":"This section will guide you through the process of submitting jobs to the EKS Cluster by modifying the workload configuration files.","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Pre-Submission Requirements:","type":"text"}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Environment Prerequisites","type":"text","marks":[{"type":"link","attrs":{"href":"https://exostellar.atlassian.net/wiki/spaces/ED/pages/99778571"}}]}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Infrastructure Optimizer Management Server","type":"text","marks":[{"type":"link","attrs":{"href":"https://exostellar.atlassian.net/wiki/pages/createpage.action?spaceKey=ED&title=Installing%20Management%20Server&linkCreation=true&fromPageId=134053943"}}]}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Tuned EKS Cluster","type":"text","marks":[{"type":"link","attrs":{"href":"https://exostellar.atlassian.net/wiki/pages/createpage.action?spaceKey=ED&title=Integrating%20with%20EKS&linkCreation=true&fromPageId=134053943"}}]}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Exostellar Karpenter","type":"text","marks":[{"type":"link","attrs":{"href":"https://exostellar.atlassian.net/wiki/spaces/ED/pages/109379651"}}]}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Configured Profile","type":"text","marks":[{"type":"link","attrs":{"href":"https://exostellar.atlassian.net/wiki/spaces/ED/pages/108462128"}}]}]}]}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Submitting a Single Pod","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"Step 1: Modifying the Workload Pod YAML File","type":"text"}]},{"type":"paragraph","content":[{"text":"To ensure that your workload runs on Exostellar nodes scheduled by the Exostellar Karpenter and block Karpenter from voluntarily disrupting your workload, you need to set affinity settings and annotations in your workload YAML file. Below is an example of how to modify your YAML file to include these settings:","type":"text"}]},{"type":"codeBlock","attrs":{"language":"yaml"},"content":[{"text":"apiVersion: apps/v1\nkind: Deployment\nmetadata:\n name: nginx\nspec:\n selector:\n matchLabels:\n app: nginx\n replicas: 1\n template:\n metadata:\n labels:\n app: nginx\n spec:\n tolerations:\n - key: \"exokarpenter.sh/x-compute\"\n operator: \"Exists\"\n effect: \"NoSchedule\"\n affinity:\n nodeAffinity:\n requiredDuringSchedulingIgnoredDuringExecution:\n nodeSelectorTerms:\n - matchExpressions:\n - key: exokarpenter.sh/nodepool\n operator: In\n values:\n - pool-a\n containers:\n - name: nginx\n image: nginx:1.14.2\n ports:\n - containerPort: 80\n resources:\n requests:\n cpu: 1","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"Step 2: Adding Node Labels in Exostellar Karpenter NodePool (optional)","type":"text"}]},{"type":"paragraph","content":[{"text":"If your workload requires scheduling on nodes with specific labels, it is required to configure Exostellar Karpenter NodePool so nodes are created with needed labels in the autoscaling process. To ensure that Exostellar Karpenter provisions nodes with the appropriate labels, you need to update the NodePool configuration with the following command: ","type":"text"}]},{"type":"codeBlock","content":[{"text":"kubectl edit exonodepool pool-a","type":"text"}]},{"type":"paragraph","content":[{"text":"An example NodePool configuration shown below creates nodes that has ","type":"text"},{"text":"jobtype","type":"text","marks":[{"type":"code"}]},{"text":" of ","type":"text"},{"text":"batch","type":"text","marks":[{"type":"code"}]},{"text":" and ","type":"text"},{"text":"nodeFamily","type":"text","marks":[{"type":"code"}]},{"text":" of ","type":"text"},{"text":"c5","type":"text","marks":[{"type":"code"}]},{"text":":","type":"text","marks":[{"type":"em"}]}]},{"type":"codeBlock","attrs":{"language":"yaml"},"content":[{"text":"apiVersion: karpenter.sh/v1beta1\nkind: ExoNodePool\nmetadata:\n name: pool-a\nspec:\n limits:\n cpu: \"400\"\n template:\n metadata:\n labels:\n jobtype: batch\n nodeFamily: c5\n spec:\n nodeClassRef:\n name: pool-a\n requirements:\n - key: topology.kubernetes.io/zone\n operator: In\n values:\n - us-east-1a\n resources: {}\nstatus: {}","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"Step 3: Submitting the Pod","type":"text"}]},{"type":"paragraph","content":[{"text":"After modifying the pod YAML file, submit the job to the EKS Cluster just like you would run a regular pod:","type":"text"}]},{"type":"codeBlock","attrs":{"language":"shell"},"content":[{"text":"kubectl apply -f my-nginx.yaml","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"Post-Submission Results","type":"text"}]},{"type":"paragraph","content":[{"text":"Exostellar Karpenter will automatically bring up the node that is suitable for your request, to check the new node that has been added:","type":"text"}]},{"type":"codeBlock","attrs":{"language":"shell"},"content":[{"text":"kubectl get nodes -A","type":"text"}]},{"type":"paragraph","content":[{"text":"The created node has ","type":"text"},{"text":"x-compute","type":"text","marks":[{"type":"code"}]},{"text":" as part of the name.","type":"text"}]},{"type":"codeBlock","attrs":{"language":"shell"},"content":[{"text":"NAME STATUS ROLES AGE VERSION\nip-192-0-128-xxx.us-east-2.x-compute.internal Ready 40s v1.29.3-eks-ae9a62a","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Scaling your Workloads","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"Step 1: Modifying the Workload YAML File","type":"text"}]},{"type":"paragraph","content":[{"text":"Similar to the above, here is an example workload YAML file:","type":"text"}]},{"type":"codeBlock","attrs":{"language":"yaml"},"content":[{"text":"apiVersion: apps/v1\nkind: Deployment\nmetadata:\n name: my-nginx\n annotations:\n karpenter.sh/do-not-disrupt: \"true\"\nspec:\n replicas: 100\n selector:\n matchLabels:\n app: my-nginx\n template:\n metadata:\n labels:\n app: my-nginx\n spec:\n tolerations:\n - key: \"exokarpenter.sh/x-compute\"\n operator: \"Exists\"\n effect: \"NoSchedule\"\n affinity:\n nodeAffinity:\n requiredDuringSchedulingIgnoredDuringExecution:\n nodeSelectorTerms:\n - matchExpressions:\n - key: exokarpenter.sh/nodepool\n operator: In\n values:\n - pool-a\n containers:\n - name: nginx\n image: nginx:1.14.2\n ports:\n - containerPort: 80\n resources:\n requests:\n cpu: 1","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"Step 2: Submitting the Workload","type":"text"}]},{"type":"paragraph","content":[{"text":"After modifying the YAML file, submit the workload to the EKS Cluster:","type":"text"}]},{"type":"codeBlock","attrs":{"language":"shell"},"content":[{"text":"kubectl apply -f deployment.yaml","type":"text"}]},{"type":"heading","attrs":{"level":4},"content":[{"text":"Post-Submission Results","type":"text"}]},{"type":"paragraph","content":[{"text":"Exostellar Karpenter will automatically bring up all nodes required for your request as above. To check the deployment status:","type":"text"}]},{"type":"codeBlock","attrs":{"language":"shell"},"content":[{"text":"kubectl get deployment -A","type":"text"}]},{"type":"paragraph","content":[{"text":"You will see:","type":"text"}]},{"type":"codeBlock","attrs":{"language":"shell"},"content":[{"text":"NAMESPACE NAME READY UP-TO-DATE AVAILABLE AGE\ndefault my-nginx 100/100 100 100 6m3s","type":"text"}]},{"type":"paragraph","content":[{"text":"To check all created pods:","type":"text"}]},{"type":"codeBlock","attrs":{"language":"shell"},"content":[{"text":"kubectl get pod -A","type":"text"}]},{"type":"paragraph","content":[{"text":"Results (only showing the top 10 lines):","type":"text"}]},{"type":"codeBlock","attrs":{"language":"shell"},"content":[{"text":"NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES\ndefault my-nginx-7587f74b9b-2jsjf 1/1 Running 0 63m 192.0.131.16 ip-192-0-132-33.us-east-2.x-compute.internal \ndefault my-nginx-7587f74b9b-2vkg6 1/1 Running 0 63m 192.0.128.55 ip-192-0-133-107.us-east-2.x-compute.internal \ndefault my-nginx-7587f74b9b-4d2pp 1/1 Running 0 63m 192.0.128.48 ip-192-0-133-107.us-east-2.x-compute.internal \ndefault my-nginx-7587f74b9b-4g4p5 1/1 Running 0 63m 192.0.141.70 ip-192-0-129-67.us-east-2.x-compute.internal \ndefault my-nginx-7587f74b9b-4n4bv 1/1 Running 0 63m 192.0.130.213 ip-192-0-142-59.us-east-2.x-compute.internal \ndefault my-nginx-7587f74b9b-5hxm8 1/1 Running 0 63m 192.0.140.133 ip-192-0-134-198.us-east-2.x-compute.internal \ndefault my-nginx-7587f74b9b-5jzlk 1/1 Running 0 63m 192.0.131.212 ip-192-0-132-33.us-east-2.x-compute.internal \ndefault my-nginx-7587f74b9b-5mxqt 1/1 Running 0 63m 192.0.130.208 ip-192-0-142-59.us-east-2.x-compute.internal \ndefault my-nginx-7587f74b9b-5nv76 1/1 Running 0 63m 192.0.131.250 ip-192-0-138-106.us-east-2.x-compute.internal \ndefault my-nginx-7587f74b9b-5zt54 1/1 Running 0 63m 192.0.131.218 ip-192-0-132-33.us-east-2.x-compute.internal ","type":"text"}]}],"version":1}

Browser not supported