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

refactor: Migrate Ray blueprint to Data-on-EKS #1443

Closed
wants to merge 12 commits into from

Conversation

askulkarni2
Copy link
Contributor

@askulkarni2 askulkarni2 commented Feb 20, 2023

‼️ PLEASE READ THIS FIRST ‼️

The direction for EKS Blueprints will soon shift from providing an all-encompassing, monolithic "framework" and instead focus more on how users can organize a set of modular components to create the desired solution on Amazon EKS. We have updated the examples to show how we use the https://github.com/terraform-aws-modules/terraform-aws-eks for EKS cluster and node group creation. We will not be accepting any PRs that apply to EKS cluster or node group creation process. Any such PR may be closed by the maintainers.

We are hitting also the pause button on new add-on creations at this time until a future roadmap for add-ons is finalized. Please do not submit new add-on PRs. Any such PR may be closed by the maintainers.

Please track progress, learn what's new and how the migration path would look like to upgrade your current Terraform deployments. We welcome the EKS Blueprints community to continue the discussion in issue #1421

What does this PR do?

The PR removes the kuberay experimental add-on from the eks-blueprints repo. The Ray blueprint has been moved to the Data-on-EKS repo and new PR was created to move the kuberay-operator helm chart deployment in the blueprint. Further enhancements to the Ray blueprint will be made in the data-on-eks repo.

Motivation

More

  • Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
  • Yes, I have updated the docs for this feature
  • Yes, I ran pre-commit run -a with this PR

For Moderators

  • E2E Test successfully complete before merge?

Additional Notes

@askulkarni2 askulkarni2 requested a review from a team as a code owner February 20, 2023 19:33
@askulkarni2 askulkarni2 temporarily deployed to EKS Blueprints Test February 20, 2023 19:33 — with GitHub Actions Inactive
@askulkarni2 askulkarni2 changed the title Migrate Ray blueprint to Data-on-EKS chore: Migrate Ray blueprint to Data-on-EKS Feb 20, 2023
@askulkarni2 askulkarni2 changed the title chore: Migrate Ray blueprint to Data-on-EKS refactor: Migrate Ray blueprint to Data-on-EKS Feb 20, 2023
@askulkarni2 askulkarni2 marked this pull request as draft February 20, 2023 19:36
@askulkarni2 askulkarni2 temporarily deployed to EKS Blueprints Test February 20, 2023 19:57 — with GitHub Actions Inactive
@askulkarni2 askulkarni2 temporarily deployed to EKS Blueprints Test March 14, 2023 22:22 — with GitHub Actions Inactive
@askulkarni2
Copy link
Contributor Author

No longer needed.

@askulkarni2 askulkarni2 deleted the ray-migrate-to-doeks branch March 23, 2023 14:14
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.

[BUG] Ray Plan fails when Route53 DNS is not provided
1 participant