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

Handle aws-node 1.7 initContainer properly #2732

Merged
merged 1 commit into from Oct 13, 2020

Conversation

icereed
Copy link
Contributor

@icereed icereed commented Oct 13, 2020

Description

Since version 1.7 of AWS VPC CNI plugin for Kubernetes
the DaemonSet consists additionally of one initContainer.

This initContainer needs the same treatment as the main container regarding
usage of the regional image.

Otherwise the consequence would be a failing pod in China regions
or slow image pulls in other regions than us-west-2.

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

@michaelbeaumont michaelbeaumont changed the base branch from master to release-0.30 October 13, 2020 10:23
@michaelbeaumont
Copy link
Contributor

@icereed I want to include this in the next RC, can you rebase on release-0.30?

@icereed
Copy link
Contributor Author

icereed commented Oct 13, 2020

Hi @michaelbeaumont,

thanks for the quick reply! I rebased now 😄

Since version 1.7 of AWS VPC CNI plugin for Kubernetes
the DaemonSet consists additionally of one initContainer.

This initContainer needs the same treatment as the main container regarding
usage of the regional image.

Otherwise the consequence would be a failing pod in China regions
or slow image pulls in other regions than us-west-2.
@icereed
Copy link
Contributor Author

icereed commented Oct 13, 2020

Tested manually, too! 👍

@icereed
Copy link
Contributor Author

icereed commented Oct 13, 2020

In terms of planning @michaelbeaumont, would the RC be available today or tomorrow? If no, I would look into options how to include a self-build binary into my tooling in order to fix an issue we have in China regions.
If it would already be available, I would directly use it. 👍

@michaelbeaumont michaelbeaumont merged commit b4d7f1a into eksctl-io:release-0.30 Oct 13, 2020
@michaelbeaumont
Copy link
Contributor

@icereed I'm preparing a release as we speak, should be at the latest this evening (CEST time)

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

Successfully merging this pull request may close these issues.

None yet

2 participants