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

Feature/trino on eks #441

Closed
wants to merge 34 commits into from

Conversation

youngjeong46
Copy link
Contributor

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.

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

youngjeong46 and others added 30 commits July 21, 2023 10:43
changed image file extensions from .png to .PNG
Changed NodeSelector for worker to be deployed on spot instances
… 4 or above

Using single AZ in Karpenter NodePool to avoid inter-AZ data transfer costs for big data workloads like Trino
Create Glue database, crawler and table in same region where Trino on EKS is deployed
specify region to create Glue database, crawler and table in same region as Trino on EKS deployment
added FT execution example, Final cleanup instructions
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.

2 participants