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

Difference between pre and post 1.18 addons #4080

Closed
Callisto13 opened this issue Aug 12, 2021 · 1 comment
Closed

Difference between pre and post 1.18 addons #4080

Callisto13 opened this issue Aug 12, 2021 · 1 comment
Labels
kind/help Request for help

Comments

@Callisto13
Copy link
Contributor

Copied from conversation in Slack to create searchable context

Hi, what’s different between EKS add-ons in eks v1.18 above, [when] we manage it our self when creating cluster from eksctl , is there any different between eksctl update addon xxxx with eksctl utils update-xxxx ? thanks in advance…

@Callisto13 Callisto13 added the kind/help Request for help label Aug 12, 2021
@Callisto13
Copy link
Contributor Author

Callisto13 commented Aug 12, 2021

response from @aclevername

EKS Add-ons are managed by EKS, meaning that they monitor the add-on to ensure its functioning and provide updates. eksctl create/get/update/delete addon are all supported, as well as eksctl utils describe-addon-versions. It's essentially the new and recommended way to deploy add-ons.

The legacy pre-1.18 method that you update via eksctl utils update-xxx hands the responsibility of updating the add-on to eksctl (we hard-code into eksctl what image version the addon should be using for a given EKS version). This method is still supported, however I believe EKS will slowly make addons enabled by default over the coming versions, so switching to EKS add-ons is advisable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/help Request for help
Projects
None yet
Development

No branches or pull requests

1 participant