forked from awslabs/amazon-eks-ami
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Unified changes with upstream v20230703 #29
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When replaying user-data in testing will bail user-data when strict... ``` mv: cannot stat ‘/etc/eks/iptables-restore.service’: No such file or directory Exited with error on line 424 ```
Co-authored-by: ljosyula <ljosyula@amazon.com>
* Revert "DNS_CLUSTER_IP cannot be specified in IPv6 Cluster (awslabs#860)" This reverts commit 0282397. * updating the deprecated version in eks template Co-authored-by: Ravi Sinha <ravsinha@amazon.com>
Some automated scanning tools may flag vulnerabilities in old kernels that are not actually in use.
* Updating Makefile and install script for 1.23 version * Removing Makefile changes
This adds support, via new bootstrap flags (--enable-local-outpost), for local control planes on Outpost, specifically when the Outpost is disconnected from its parent region.
Updating the 1.22 binaries including their build date and build version
10M resulted in insufficient logs for investigation in too many cases. Rather than removing the limit entirely, this raises it to include the entire /var/log/messages in most cases while making the resulting archive easy to pass between support and service teams.
Allows `ami_regions` to be passed through the `make` line, which will instruct Packer to copy the resulting AMI(s) to additional regions.
We recently updated the 1.20 binaries with latest build dates and those respective binaries have been uploaded to the s3 bucket.
Co-authored-by: Ravi Sinha <ravsinha@amazon.com>
Co-authored-by: ljosyula <ljosyula@amazon.com>
Co-authored-by: ljosyula <ljosyula@amazon.com>
…st-1 support (awslabs#1294) Co-authored-by: ljosyula <ljosyula@amazon.com>
Co-authored-by: cartermckinnon <cartermckinnon@users.noreply.github.com>
* AMI Release v20230509 --------- Co-authored-by: Zaid Farooq <zaidaf@amazon.com>
Update the CHANGELOG.md for the v20230513 AMI Release
Update changelog for `v20230526` release
Co-authored-by: Ravi Sinha <ravsinha@amazon.com>
* Simplify CircleCI pipeline * Use upstream Makefile * Use fluence-eks-worker-al2-variable.json to set variables * Cleanups. Delete healthchecks and service configurations not existing in the upstream repo
…-worker.sh script
j3-fluence
approved these changes
Aug 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes:
Update our respository with upstream AWSLabs.