refactor: Migrate Ray blueprint to Data-on-EKS #1443
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
askulkarni2
temporarily deployed
to
EKS Blueprints Test
GitHub Actions
Inactive
askulkarni2
changed the title
askulkarni2
changed the title
askulkarni2
temporarily deployed
to
EKS Blueprints Test
GitHub Actions
Inactive
askulkarni2
temporarily deployed
to
EKS Blueprints Test
GitHub Actions
Inactive
askulkarni2
had a problem deploying
to
EKS Blueprints Test
GitHub Actions
Failure
|
No longer needed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
pre-commit run -awith this PRFor Moderators
Additional Notes