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

Don't replace service account with update-aws-node #2459

Merged
merged 3 commits into from Jul 21, 2020

Conversation

michaelbeaumont
Copy link
Contributor

@michaelbeaumont michaelbeaumont commented Jul 21, 2020

Description

Fixes #1645

Checklist

  • Added tests that cover your change (if possible)
  • Added/modified documentation as required (such as the README.md, or the userdocs directory)
  • Manually tested
  • Added labels for change area (e.g. area/nodegroup), target version (e.g. version/0.12.0) and kind (e.g. kind/improvement)
  • Make sure the title of the PR is a good description that can go into the release notes

return false, err
}
if exists {
continue
Copy link
Contributor

Choose a reason for hiding this comment

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

It'd be consistent to have a log message indicating that it was skipped, somewhat like the "pretend it was replaced" log message for CustomResourceDefinition directly above.

@TBBle
Copy link
Contributor

TBBle commented Jul 21, 2020

You'll need to update the test as well, since this changes the behaviour when facing a default EKS install, or in fact any EKS install that hasn't had the aws-node manually removed.

@michaelbeaumont michaelbeaumont merged commit 08ebdc1 into eksctl-io:master Jul 21, 2020
@michaelbeaumont michaelbeaumont deleted the aws-node branch July 21, 2020 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

eksctl utils update-aws-node wiping service account annotation
3 participants