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: Update EFA device plugin to use the EKS charts repo #26

Merged
merged 3 commits into from
Mar 16, 2024

Conversation

alanty
Copy link
Contributor

@alanty alanty commented Mar 12, 2024

What does this PR do?

Updates aws-efa-k8s-device-plugin.tf to use the eks-charts repo (https://github.com/aws/eks-charts/tree/master/stable/aws-efa-k8s-device-plugin) instead of a local copy of the device plugin chart

Motivation

this should make it easier to update later and includes the latest updates and instance types in the nodeAffinity.

More

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

For Moderators

  • E2E Test successfully complete before merge?

Additional Notes

@alanty alanty requested a review from a team as a code owner March 12, 2024 21:30
Copy link
Contributor

@lusoal lusoal left a comment

Choose a reason for hiding this comment

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

@vara-bonthu to validate

repository = try(var.aws_efa_k8s_device_plugin_helm_config["repository"], null)
chart = try(var.aws_efa_k8s_device_plugin_helm_config["chart"], "${path.module}/helm-charts/aws-efa-k8s-device-plugin")
version = try(var.aws_efa_k8s_device_plugin_helm_config["version"], "0.1.0")
repository = try(var.aws_efa_k8s_device_plugin_helm_config["repository"], "https://aws.github.io/eks-charts")
Copy link
Contributor

Choose a reason for hiding this comment

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

I like to use the upstream repo instead of our local one, have you validated that all the configs that we are using by default in the values.yaml file are used into the default chart values? I'm asking that because people could be relying in the default values. @vara-bonthu need you on that.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thats a good call, I haven't checked what those defaults are in the local copy. I'll double check those and make sure we aren't breaking anything.

We may have added tolerations that the upstream doesn't.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Looking at a diff of the values:

  • Upstream Drops beta.kubernetes.io/instance-type from the label selector (Starting in v1.17, this label is deprecated in favor of node.kubernetes.io/instance-type.)
  • Upstream moves version from v0.3.3 to v0.4.4
  • upstream has added a requests block to the values:
resources:
   requests:
     cpu:     10m
     memory:  20Mi
  • our Local copy has a toleration to run everywhere, upstream values has an empty toleration config.
tolerations:
  - operator: Exists    # DaemonSet is tolerant of any taints, regardless of the key or value of the taint.
  - key: CriticalAddonsOnly
    operator: Exists

I'll add that toleration to our addon config but I think the other changes are ok.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@alanty alanty changed the title [feat] Update EFA device plugin to use the EKS charts repo feat: Update EFA device plugin to use the EKS charts repo Mar 14, 2024
Copy link
Contributor

@vara-bonthu vara-bonthu left a comment

Choose a reason for hiding this comment

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

LGTM

@vara-bonthu vara-bonthu merged commit 3f58acc into aws-ia:main Mar 16, 2024
7 of 8 checks passed
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.

[feature] update EFA plugin addon to use eks-charts location instead of local copy
3 participants