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.

Sign up for GitHub

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: Install AWS EKS Add-on #167

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
+58 −40
Open

feat: Install AWS EKS Add-on #167

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
f05b333
get upgrade working
Jan 9, 2024
bb5eaa6
install EKS VPC-CNI Add-on
Jan 11, 2024
803acbd
cleanup
Jan 11, 2024
82127cd
Merge branch 'main' into george-test
Jan 22, 2024
6898ebb
remove extra spaces
Feb 9, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
install EKS VPC-CNI Add-on
George Scott committed Jan 11, 2024
commit bb5eaa6fa486bb95e15548ca164f97051890da0b
21 changes: 12 additions & 9 deletions modules/app_eks/add-ons.tf
View file
Original file line number Diff line number Diff line change
@@ -1,27 +1,30 @@
resource "aws_eks_addon" "ebs_csi" {
depends_on = [
module.eks,
aws_eks_addon.vpc_cni
]

addon_name = "aws-ebs-csi-driver"
addon_version = "v1.25.0-eksbuild.1"
cluster_name = var.namespace
preserve = false
resolve_conflicts = "OVERWRITE"
depends_on = [
module.eks,
aws_eks_addon.vpc_cni
]

}

resource "aws_eks_addon" "vpc_cni" {
depends_on = [
module.eks,
aws_iam_openid_connect_provider.eks,
aws_iam_role_policy_attachment.vpc_cni
]

addon_name = "vpc-cni"
addon_version = "v1.13.0-eksbuild.1"
Copy link
Contributor

Choose a reason for hiding this comment

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

This version is different than the deleted one, just wanna make sure this is the right one

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes. One of the things that can be used to differentiate the self-managed plugin vs. the EKS add-on are the version numbers. This particular version is the next "in line" -- most of our clusters, if not all, are running v.1.12 of the plugin, and I'm gunning for keeping the AWS recommendation of upgrading the CNI one minor version at a time.

cluster_name = var.namespace
preserve = false
resolve_conflicts = "OVERWRITE"
service_account_role_arn = aws_iam_role.node.arn
depends_on = [
module.eks,
aws_iam_openid_connect_provider.eks,
aws_iam_role_policy_attachment.vpc_cni
]
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Does this change have any impact on existing workloads?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It should not have any impact at all.


#########################################