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: Spark-operator update karpenter to v1 #673

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

alanty
Copy link
Contributor

@alanty alanty commented Oct 10, 2024

What does this PR do?

updates the charts/configs for karpenter v1 in the spark-operator blueprint.
the karpenter resources have already been bumped, this moves the helm chart to 1.0.0 (latest).

Motivation

#669 came up when i was creating a copy of the solution today.

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?

@@ -103,7 +103,7 @@ module "eks_blueprints_addons" {
}
}
karpenter = {
chart_version = "0.37.0"
chart_version = "1.0.0"
Copy link
Collaborator

Choose a reason for hiding this comment

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

You might need to uplift data addons tag and update the Karpenter resources to v1.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good call. I was pulling v1.34.0 but we should set that as the min.

When i rolled this out the existing karpenter resource configs seemed to get created as v1 but i'm still working through the configs to see if they need updates to the spec.

@@ -3,7 +3,7 @@
#---------------------------------------------------------------
module "eks_data_addons" {
source = "aws-ia/eks-data-addons/aws"
version = "~> 1.30" # ensure to update this to the latest/desired version
version = "~> 1.34" # ensure to update this to the latest/desired version
Copy link
Contributor

Choose a reason for hiding this comment

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

please use a fixed version instead, in this case it should be 1.34.0 ... we just had a problem because of the ~> config

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think I was able to merge all the upstream changes and keep the versions you mention here (Addons 1.34.0 and karpenter 1.0.6).

Copy link
Contributor

Choose a reason for hiding this comment

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

awesome, this LGTM!

@@ -417,7 +417,7 @@ module "eks_blueprints_addons" {
}
}
karpenter = {
chart_version = "v0.34.0"
chart_version = "1.0.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

please use the latest version 1.0.6

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think I was able to merge all the upstream changes and keep the versions you mention here (Addons 1.34.0 and karpenter 1.0.6).

Copy link
Contributor

Choose a reason for hiding this comment

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

awesome, this LGTM!

@alanty alanty changed the title feat: spark-operator update karpenter to v1 feat: Spark-operator update karpenter to v1 Oct 14, 2024
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.

3 participants