Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: JARK stack update with Argo Workflows, Karpenter and KubeRay #487

Merged
merged 7 commits into from
Apr 5, 2024

Conversation

vara-bonthu
Copy link
Collaborator

@vara-bonthu vara-bonthu commented Apr 5, 2024

What does this PR do?

🛑 Please open an issue first to discuss any significant work and flesh out details/direction - we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.

  • JARK stack updated with Argo workflows, Karpenter addons
  • KubeRay Operator upgraded
  • StableDiffusion example added with RayServe2.10 with autoscaling and servecinfigv2
  • EFA disabled by default
  • New folder structure created for the examples that shows training and inference

NOTE: Website Doc for this deployment will be raised as a Part2 PR

Motivation

More

  • Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
  • Mandatory for new blueprints. Yes, I have added a example to support my blueprint PR
  • Mandatory for new blueprints. Yes, I have updated the website/docs or website/blog section for this feature
  • Yes, I ran pre-commit run -a with this PR. Link for installing pre-commit locally

For Moderators

  • E2E Test successfully complete before merge?

Additional Notes

Copy link
Contributor

@alanty alanty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the updates and think i follow the example files, we could really use docs on this stack.

enable_kuberay_operator = true
enable_nvidia_device_plugin = true
nvidia_device_plugin_helm_config = {
version = "v0.15.0-rc.2"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are there features we need in the RC release?

imo if we're using the release candidate we should ensure we update this again when the "full" 0.15.x release is out(or better, bump the addon default).

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1. We will need to keep this up to date on an ongoing basis based on the number of issues we keep encountering.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree. I had to change to the latest version to verify the NVIDIA Device plugin issue that we were facing. It turns out to be an EKS AMI issue but not the NVIDIA device plugin.

I will change this to stable version v0.14.5 for now

it's always better for us to lock the blueprints addons to a specific version to avoid failures with newer releases

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should use 0.14.5 major release for now instead of release candidate

nvidia_device_plugin_helm_config = {
version = "v0.15.0-rc.2"
name = "nvidia-device-plugin"
values = [
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor structure thing.

this PR moves the Nvidia plugin values inline at ~188, I added a similar toleration block for the efa device plugin in aws-efa-k8s-device-plugin-values.yaml. Is there a preference or style to follow?

I like having the smaller values blocks inline as it makes things a bit easier to read without having to jump between files. Though the values in a separate file is a bit easier syntax and more like helm.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't necessarily have a preference one way or the other. In general the guideline is small changes can go inline, large changes in a separate file.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 to Apoorva. If it's a small config easy to embed into the code otherwise, create a dedicated yaml file

Copy link
Collaborator

@askulkarni2 askulkarni2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the awesome PR! LGTM!

enable_kuberay_operator = true
enable_nvidia_device_plugin = true
nvidia_device_plugin_helm_config = {
version = "v0.15.0-rc.2"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1. We will need to keep this up to date on an ongoing basis based on the number of issues we keep encountering.

nvidia_device_plugin_helm_config = {
version = "v0.15.0-rc.2"
name = "nvidia-device-plugin"
values = [
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't necessarily have a preference one way or the other. In general the guideline is small changes can go inline, large changes in a separate file.

securityGroupSelectorTerms:
tags:
Name: ${module.eks.cluster_name}-node
instanceStorePolicy: RAID0
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❤️

@@ -13,7 +13,7 @@ variable "region" {

variable "eks_cluster_version" {
description = "EKS Cluster version"
default = "1.27"
default = "1.29"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

@sanjeevrg89
Copy link
Contributor

Overall, LGTM as we. Thank you @vara-bonthu

Copy link
Collaborator

@ratnopamc ratnopamc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Copy link
Contributor

@sanjeevrg89 sanjeevrg89 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, approving the request

enable_kuberay_operator = true
enable_nvidia_device_plugin = true
nvidia_device_plugin_helm_config = {
version = "v0.15.0-rc.2"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should use 0.14.5 major release for now instead of release candidate

@vara-bonthu vara-bonthu merged commit fcda963 into main Apr 5, 2024
55 of 56 checks passed
@vara-bonthu vara-bonthu deleted the feat-sd-jark branch April 5, 2024 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants