Bump the AWS providers to v2.8.1 - #481
Merged
Merged
Conversation
ldalorion
force-pushed
the
bump-aws-providers-v2.8.1
branch
from
September 30, 2026 23:19
48a43c6 to
10c717b
Compare
provider-aws-eks v2.6.0 reverts cluster-autoscaler's changes to an EKS node group. compose-eks-cluster seeds desiredSize only in initProvider and drops LateInitialize so the autoscaler can own it, but upjet before v2.5.0 never ignored initProvider fields inside a converted singleton list. So the provider sets desiredSize back to its initProvider value on its next reconcile, and the AWS Scaling Group terminates the node the cluster-autoscaler added. crossplane/upjet#728 fixed this in upjet v2.5.0, which provider-upjet-aws v2.8.1 builds with. v2.8.1 is the latest upstream release, so it stays pullable without a subscription under the pinning rule from modelplaneai#170. This bumps provider-aws-eks, -ec2, -iam and -efs from v2.6.0 to v2.8.1 and regenerates the schemas and schemas/.lock.json against them. Fixes modelplaneai#480. Signed-off-by: L. Dalorion Johnson <ldalorion@users.noreply.github.com>
ldalorion
force-pushed
the
bump-aws-providers-v2.8.1
branch
from
September 30, 2026 23:29
10c717b to
e3c91c6
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 your changes
Fixes #480.
provider-aws-eks v2.6.0 reverts cluster-autoscaler's changes to EKS node groups. compose-eks-cluster seeds
desiredSizeonly ininitProviderand dropsLateInitialize(#183), but upjet before v2.5.0 never ignoredinitProviderfields inside a converted singleton list. (crossplane-contrib/provider-upjet-aws#2044). The provider setsdesiredSizeback on its next reconcile, and the aws scaling group terminates the node the cluster-autoscaler added. This affects the system pool and every autoscaled GPU pool.crossplane/upjet#728 fixed it in upjet v2.5.0, which provider-upjet-aws v2.8.1 builds with (crossplane-contrib/provider-upjet-aws#2245). v2.8.1 is the latest upstream release, so it follows the pinning rule from #170. The downstream
xpkg.upbound.io/upbound/provider-aws-{eks,ec2,iam,efs}:v2.8.1packages pull without credentials.This bumps the four AWS providers from v2.6.0 to v2.8.1 and regenerates
schemas/python/andschemas/.lock.json. The v2.7.0 and v2.8.0 release notes list breaking changes only in kinds Modelplane doesn't compose. It doesn't touch the GCP providers.I tested it against a real EKS cluster with a NodeGroup composed the way compose-eks-cluster composes one (the repro in #480), with a 1-minute poll:
aws eks update-nodegroup-config ... desiredSize=2, CloudTrail shows anUpdateNodegroupConfigback todesiredSize: 1fromterraform-provider-aws7 seconds later.Synced=Truewithstatus.atProvider.scalingConfig.desiredSize: 2, and CloudTrail shows no providerUpdateNodegroupConfig.I have:
nix flake check(or./nix.sh flake check) and made sure it passes.Added or updated tests covering any composition function changes.No composition function changes.git commit -s.