Update first-party Pulumi dependencies #1540
Closed
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
![pulumi-renovate[bot]](https://avatars.githubusercontent.com/u/21992475?s=60&v=4){kind=small}
pulumi-renovate
bot
added
dependencies
Does the PR have any schema changes?Found 60 breaking changes: Resources
Types
|
pulumi-renovate
bot
force-pushed
the
renovate/pulumi
branch
2 times, most recently
from
66a5967 to
379987d
Compare
|
@blampe I'm quite intrigued by this. After the main branch got a Renovate config, the change is better I think as it's not touching the sdk/* folder but where is this coming from? Is this a yarn version mismatch? |
|
The The schema.json needs to be recomputed as part of the update, this can be done by hooking up more logic into
|
t0yv0
reviewed
Dec 18, 2024
| @@ -3,15 +3,16 @@ module github.com/pulumi/pulumi-eks/examples/aws-go-eks-helloworld | |||
| go 1.21 | |||
|
|
|||
| require ( | |||
| github.com/pulumi/pulumi-eks/sdk/v3 v3.0.0-alpha.6 | |||
|
Trying a manual correction version on top: #1541 |
@t0yv0 I switched us to a fatter image with built-in runtimes https://github.com/pulumi/home/pull/3774 and I think this is a side effect of it picking up the global yarn v5. The slimmer image seemed to correctly detect and install yarn v1, so I'll revert the image and see if that helps. Fat images aren't the future anyway. Edit: yeah it looks like it's happier with that. |
pulumi-renovate
bot
force-pushed
the
renovate/pulumi
branch
from
379987d to
03fcf45
Compare
ℹ Artifact update noticeFile name: examples/aws-go-eks-helloworld/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: examples/cluster-go/step1/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: examples/extra-sg-go/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: examples/managed-nodegroups-go/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
|
This is looking better! I can tackle this one by fixing what |
pulumi-renovate
bot
force-pushed
the
renovate/pulumi
branch
2 times, most recently
from
deef8f1 to
936f82d
Compare
pulumi-renovate
bot
force-pushed
the
renovate/pulumi
branch
from
936f82d to
5d1be51
Compare
t0yv0
added a commit
that referenced
this pull request
Dec 20, 2024
Tweaking renovate config to more aggressively regenerate the files but not to build them. Optimizing not re-downloading java-gen. Hoping to get #1540 past the point where it is failing.
|
Interesting Looks like it still is having trouble. Is |
|
Retry on top of #1551 |
pulumi-renovate
bot
force-pushed
the
renovate/pulumi
branch
from
5d1be51 to
dc85231
Compare
pulumi-renovate
bot
changed the title
|
Rebasing again after editing Make to automatically install pulumictl should one not be found in the environment. |
t0yv0
changed the title
pulumi-renovate
bot
force-pushed
the
renovate/pulumi
branch
from
dc85231 to
8f03a9f
Compare
pulumi-renovate
bot
changed the title
pulumi-renovate
bot
force-pushed
the
renovate/pulumi
branch
from
8f03a9f to
acfbf5a
Compare
t0yv0
changed the title
pulumi-renovate
bot
force-pushed
the
renovate/pulumi
branch
from
acfbf5a to
911becf
Compare
pulumi-renovate
bot
changed the title
t0yv0
changed the title
|
Looks like the previous config had fileFilters misconfigured per #1557 Trying again. |
pulumi-renovate
bot
force-pushed
the
renovate/pulumi
branch
from
911becf to
955f1e0
Compare
pulumi-renovate
bot
changed the title
t0yv0
reviewed
Dec 23, 2024
| @@ -28,14 +28,14 @@ | |||
| }, | |||
| "java": { | |||
| "dependencies": { | |||
| "com.pulumi:aws": "6.65.0", | |||
| "com.pulumi:kubernetes": "4.18.3" | |||
| "com.pulumi:aws": "6.66.1", | |||
There was a problem hiding this comment.
Nice looks like the schema is getting automatically updated.
|
Looks like there is a remaining issue in generate/build command responsibilities, looking. The generator for Node SDK does not update sdk/nodejs/package.json and sdk/nodejs/yarn.lock but the builder does. This is unexpected. |
|
#1558 should hopefully get past this problem. |
t0yv0
changed the title
pulumi-renovate
bot
force-pushed
the
renovate/pulumi
branch
from
955f1e0 to
57e4dde
Compare
pulumi-renovate
bot
changed the title
|
There are small breaking changes in providertest upgraded here. #1541 has the manual edits appended. |
pulumi-renovate
bot
force-pushed
the
renovate/pulumi
branch
from
57e4dde to
c6c0249
Compare
pulumi-renovate
bot
force-pushed
the
renovate/pulumi
branch
from
c6c0249 to
5b43f3c
Compare
t0yv0
added a commit
that referenced
this pull request
Dec 23, 2024
This change accepts suggestions from #1540 and has two things done on top: 1. update Go test code to the newest version of providertest Let us see if the build and test passes. --------- Co-authored-by: pulumi-renovate[bot] <189166143+pulumi-renovate[bot]@users.noreply.github.com>
|
Merging this via #1541 |
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.
This PR contains the following updates:
6.65.0->6.66.1^6.0.0->6.66.1^6.50.1->6.66.1^6.52.0->6.66.1^6.56.0->6.66.1^2.0.2->2.19.0^2.0.0->2.19.04.18.3->4.19.0^4.1.1->4.19.0^4.18.3->4.19.0^4.0.0->4.19.0^0.1.6->0.1.63.143.0->3.144.1^3.0.0->3.144.1^4.0.0->4.16.8v0.0.15->v0.1.3v6.41.0->v6.66.1v6.29.0->v6.66.1v6.50.1->v6.66.1v3.0.0-alpha.6->v3.6.0v4.9.1->v4.19.0v3.143.0->v3.144.1v3.143.0->v3.144.1v3.112.0->v3.144.1v3.129.0->v3.144.1>=2.0.0,<3.0.0->>=3.6.0,<3.7.0b374cebv5->v67c54f13v0.0.20->v0.0.21Release Notes
pulumi/pulumi-aws (@pulumi/aws)
v6.66.1Compare Source
Does the PR have any schema changes?
Found 2 breaking changes:
Types
🟢"aws:alb/getListenerMutualAuthentication:getListenerMutualAuthentication": required: "advertiseTrustStoreCaNames" property has changed to Required🟢"aws:lb/getListenerMutualAuthentication:getListenerMutualAuthentication": required: "advertiseTrustStoreCaNames" property has changed to RequiredNo new resources/functions.
What's Changed
Full Changelog: pulumi/pulumi-aws@v6.66.0...v6.66.1
v6.66.0Compare Source
Does the PR have any schema changes?
Found 2 breaking changes:
Types
🟢"aws:codeconnections/HostVpcConfiguration:HostVpcConfiguration": required: "tlsCertificate" property is no longer Required🟢"aws:licensemanager/getReceivedLicenseEntitlement:getReceivedLicenseEntitlement": required: "overage" property has changed to RequiredNew resources:
apigateway/domainNameAccessAssociation.DomainNameAccessAssociationcloudfront/vpcOrigin.VpcOriginmemorydb/multiRegionCluster.MultiRegionClusternetworkmanager/dxGatewayAttachment.DxGatewayAttachmentrds/clusterSnapshotCopy.ClusterSnapshotCopyNew functions:
servicecatalog/getAppregistryAttributeGroupAssociations.getAppregistryAttributeGroupAssociationsWhat's Changed
make upstreamfrompreTestby @blampe in https://github.com/pulumi/pulumi-aws/pull/4935Full Changelog: pulumi/pulumi-aws@v6.65.0...v6.66.0
pulumi/pulumi-kubernetes (@pulumi/kubernetes)
v4.19.0Compare Source
Changed
v4.18.4Compare Source
Changed
punycodedeprecation warnings by using nativefetchinstead ofnode-fetch.https://github.com/pulumi/pulumi-kubernetes/issues/33013301)
Fixed
pulumi.com/waitForand other await annotations now correctly take precedence over default await logic.https://github.com/pulumi/pulumi-kubernetes/issues/33293329)
JSONPath expressions used with the
pulumi.com/waitForannotation will no longer hang indefinitely if they match non-primitive fields.https://github.com/pulumi/pulumi-kubernetes/issues/33453345)
[java] CRDs that contain any
x-kubernetes-*fields can now be succesfully created and managed by Pulumi.https://github.com/pulumi/pulumi-kubernetes/issues/33253325)
pulumi/pulumi (@pulumi/pulumi)
v3.144.1Compare Source
3.144.1 (2024-12-20)
Bug Fixes
v3.144.0Compare Source
3.144.0 (2024-12-20)
Features
[engine] Warn if
refreshordestroyuse older parameterized packages#18029
[sdk/dotnet] Update dotnet to 3.71.1
#18084
[auto/go] Add ConfigFile to GetConfig and SetConfig operations, add GetAllConfigWithOptions to extend GetAllConfig
#17939
[cli/plugin] Log plugin unstructured output to debug instead of info
#17943
[sdk/yaml] Update pulumi-yaml to 1.13.0
#18077
Bug Fixes
[backend/diy] Retry deletes of lock files if they fail
#18059
[auto/go] Fix potential race condition when using automation API
#18044
[auto/go] Fix "debug" flag in automation api
#18071
[cli/install] Avoid unnecessary Node.js installations
#18041
[engine] Use package load v2 in loader server so it can include paramaterization
#18072
#18021
[programgen/dotnet] Emit local dependencies in restore sources deterministically
#18026
[sdk/go] Ignore DependsOn for direct form invokes instead of raising an error
#18089
[sdk/nodejs] Respect the noCheck option from tsconfig.json
#18067
[sdk/nodejs] Gracefully handle errors that don't implement toString
#18080
[sdk/python] Fix hang on error when using uv on Windows
#18054
[sdkgen/dotnet] Compute restore sources from local dependencies and referenced packages
#18042
Miscellaneous
#18049
pulumi/providertest (github.com/pulumi/providertest)
v0.1.3Compare Source
What's Changed
Full Changelog: pulumi/providertest@v0.1.2...v0.1.3
v0.1.2Compare Source
What's Changed
Full Changelog: pulumi/providertest@v0.1.1...v0.1.2
v0.1.1Compare Source
What's Changed
provider.ReplayInvokesby @danielrbradley in https://github.com/pulumi/providertest/pull/105Full Changelog: pulumi/providertest@v0.1.0...v0.1.1
v0.1.0Compare Source
What's Changed
Texplicitly to all methods by @danielrbradley in https://github.com/pulumi/providertest/pull/102You must now pass T as the first parameter for any method which does asserts internally, as is the pattern in Go.
You can fix pretty much all usages using the following batch of
gofmtcommands:New Contributors
Full Changelog: pulumi/providertest@v0.0.15...v0.1.0
pulumi/pulumi-eks (github.com/pulumi/pulumi-eks/sdk/v3)
v3.6.0Compare Source
Does the PR have any schema changes?
Looking good! No breaking changes found.
No new resources/functions.
What's Changed
Full Changelog: v3.5.0...v3.6.0
v3.5.0Compare Source
Does the PR have any schema changes?
Found 60 breaking changes:
Resources
🟡"clusterSecurityGroup" type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup"🟡"instanceRole" type changed from "/aws/v6.18.2/schema.json#/resources/aws:iam%2Frole:Role" to "/aws/v6.65.0/schema.json#/resources/aws:iam%2Frole:Role"🟡"instanceRoles": items type changed from "/aws/v6.18.2/schema.json#/resources/aws:iam%2Frole:Role" to "/aws/v6.65.0/schema.json#/resources/aws:iam%2Frole:Role"🟡"serviceRole" type changed from "/aws/v6.18.2/schema.json#/resources/aws:iam%2Frole:Role" to "/aws/v6.65.0/schema.json#/resources/aws:iam%2Frole:Role"🟡"awsProvider" type changed from "/aws/v6.18.2/schema.json#/provider" to "/aws/v6.65.0/schema.json#/provider"🟡"clusterSecurityGroup" type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup"🟡"eksCluster" type changed from "/aws/v6.18.2/schema.json#/resources/aws:eks%2Fcluster:Cluster" to "/aws/v6.65.0/schema.json#/resources/aws:eks%2Fcluster:Cluster"🟡"eksClusterIngressRule" type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroupRule:SecurityGroupRule" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroupRule:SecurityGroupRule"🟡"instanceRoles": items type changed from "/aws/v6.18.2/schema.json#/resources/aws:iam%2Frole:Role" to "/aws/v6.65.0/schema.json#/resources/aws:iam%2Frole:Role"🟡"nodeSecurityGroup" type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup"🟡"eks:index:ClusterCreationRoleProvider": properties: "role" type changed from "/aws/v6.18.2/schema.json#/resources/aws:iam%2Frole:Role" to "/aws/v6.65.0/schema.json#/resources/aws:iam%2Frole:Role"🟡"launchTemplate" type changed from "/aws/v6.18.2/schema.json#/types/aws:eks%2FNodeGroupLaunchTemplate:NodeGroupLaunchTemplate" to "/aws/v6.65.0/schema.json#/types/aws:eks%2FNodeGroupLaunchTemplate:NodeGroupLaunchTemplate"🟡"nodeRole" type changed from "/aws/v6.18.2/schema.json#/resources/aws:iam%2Frole:Role" to "/aws/v6.65.0/schema.json#/resources/aws:iam%2Frole:Role"🟡"remoteAccess" type changed from "/aws/v6.18.2/schema.json#/types/aws:eks%2FNodeGroupRemoteAccess:NodeGroupRemoteAccess" to "/aws/v6.65.0/schema.json#/types/aws:eks%2FNodeGroupRemoteAccess:NodeGroupRemoteAccess"🟡"scalingConfig" type changed from "/aws/v6.18.2/schema.json#/types/aws:eks%2FNodeGroupScalingConfig:NodeGroupScalingConfig" to "/aws/v6.65.0/schema.json#/types/aws:eks%2FNodeGroupScalingConfig:NodeGroupScalingConfig"🟡"taints": items type changed from "/aws/v6.18.2/schema.json#/types/aws:eks%2FNodeGroupTaint:NodeGroupTaint" to "/aws/v6.65.0/schema.json#/types/aws:eks%2FNodeGroupTaint:NodeGroupTaint"🟡properties: "nodeGroup" type changed from "/aws/v6.18.2/schema.json#/resources/aws:eks%2FnodeGroup:NodeGroup" to "/aws/v6.65.0/schema.json#/resources/aws:eks%2FnodeGroup:NodeGroup"🟡"clusterIngressRule" type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroupRule:SecurityGroupRule" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroupRule:SecurityGroupRule"🟡"extraNodeSecurityGroups": items type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup"🟡"instanceProfile" type changed from "/aws/v6.18.2/schema.json#/resources/aws:iam%2FinstanceProfile:InstanceProfile" to "/aws/v6.65.0/schema.json#/resources/aws:iam%2FinstanceProfile:InstanceProfile"🟡"nodeSecurityGroup" type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup"🟡"cfnStack" type changed from "/aws/v6.18.2/schema.json#/resources/aws:cloudformation%2Fstack:Stack" to "/aws/v6.65.0/schema.json#/resources/aws:cloudformation%2Fstack:Stack"🟡"extraNodeSecurityGroups": items type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup"🟡"nodeSecurityGroup" type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup"🟡"clusterSecurityGroup" type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup"🟡"eksCluster" type changed from "/aws/v6.18.2/schema.json#/resources/aws:eks%2Fcluster:Cluster" to "/aws/v6.65.0/schema.json#/resources/aws:eks%2Fcluster:Cluster"🟡"securityGroup" type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup"🟡"securityGroupRule" type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroupRule:SecurityGroupRule" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroupRule:SecurityGroupRule"🟡"clusterIngressRule" type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroupRule:SecurityGroupRule" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroupRule:SecurityGroupRule"🟡"extraNodeSecurityGroups": items type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup"🟡"instanceProfile" type changed from "/aws/v6.18.2/schema.json#/resources/aws:iam%2FinstanceProfile:InstanceProfile" to "/aws/v6.65.0/schema.json#/resources/aws:iam%2FinstanceProfile:InstanceProfile"🟡"launchTemplateTagSpecifications": items type changed from "/aws/v6.18.2/schema.json#/types/aws:ec2%2FLaunchTemplateTagSpecification:LaunchTemplateTagSpecification" to "/aws/v6.65.0/schema.json#/types/aws:ec2%2FLaunchTemplateTagSpecification:LaunchTemplateTagSpecification"🟡"nodeSecurityGroup" type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup"🟡"autoScalingGroup" type changed from "/aws/v6.18.2/schema.json#/resources/aws:autoscaling%2Fgroup:Group" to "/aws/v6.65.0/schema.json#/resources/aws:autoscaling%2Fgroup:Group"🟡"extraNodeSecurityGroups": items type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup"🟡"nodeSecurityGroup" type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup"Types
🟡"eks:index:AccessPolicyAssociation": properties: "accessScope" type changed from "/aws/v6.18.2/schema.json#/types/aws:eks%2FAccessPolicyAssociationAccessScope:AccessPolicyAssociationAccessScope" to "/aws/v6.65.0/schema.json#/types/aws:eks%2FAccessPolicyAssociationAccessScope:AccessPolicyAssociationAccessScope"🟡"clusterIngressRule" type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroupRule:SecurityGroupRule" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroupRule:SecurityGroupRule"🟡"extraNodeSecurityGroups": items type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup"🟡"instanceProfile" type changed from "/aws/v6.18.2/schema.json#/resources/aws:iam%2FinstanceProfile:InstanceProfile" to "/aws/v6.65.0/schema.json#/resources/aws:iam%2FinstanceProfile:InstanceProfile"🟡"launchTemplateTagSpecifications": items type changed from "/aws/v6.18.2/schema.json#/types/aws:ec2%2FLaunchTemplateTagSpecification:LaunchTemplateTagSpecification" to "/aws/v6.65.0/schema.json#/types/aws:ec2%2FLaunchTemplateTagSpecification:LaunchTemplateTagSpecification"🟡"nodeSecurityGroup" type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup"🟡"awsProvider" type changed from "/aws/v6.18.2/schema.json#/provider" to "/aws/v6.65.0/schema.json#/provider"🟡"cluster" type changed from "/aws/v6.18.2/schema.json#/resources/aws:eks%2Fcluster:Cluster" to "/aws/v6.65.0/schema.json#/resources/aws:eks%2Fcluster:Cluster"🟡"clusterIamRole" type changed from "/aws/v6.18.2/schema.json#/resources/aws:iam%2Frole:Role" to "/aws/v6.65.0/schema.json#/resources/aws:iam%2Frole:Role"🟡"clusterSecurityGroup" type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup"🟡"eksNodeAccess" type changed from "/kubernetes/v4.4.0/schema.json#/resources/kubernetes:core%2Fv1:ConfigMap" to "/kubernetes/v4.18.3/schema.json#/resources/kubernetes:core%2Fv1:ConfigMap"🟡"encryptionConfig" type changed from "/aws/v6.18.2/schema.json#/types/aws:eks%2FClusterEncryptionConfig:ClusterEncryptionConfig" to "/aws/v6.65.0/schema.json#/types/aws:eks%2FClusterEncryptionConfig:ClusterEncryptionConfig"🟡"fargateProfile" type changed from "/aws/v6.18.2/schema.json#/resources/aws:eks%2FfargateProfile:FargateProfile" to "/aws/v6.65.0/schema.json#/resources/aws:eks%2FfargateProfile:FargateProfile"🟡"instanceRoles": items type changed from "/aws/v6.18.2/schema.json#/resources/aws:iam%2Frole:Role" to "/aws/v6.65.0/schema.json#/resources/aws:iam%2Frole:Role"🟡"oidcProvider" type changed from "/aws/v6.18.2/schema.json#/resources/aws:iam%2FopenIdConnectProvider:OpenIdConnectProvider" to "/aws/v6.65.0/schema.json#/resources/aws:iam%2FopenIdConnectProvider:OpenIdConnectProvider"🟡"provider" type changed from "/kubernetes/v4.4.0/schema.json#/provider" to "/kubernetes/v4.18.3/schema.json#/provider"🟡"storageClasses": additional properties type changed from "/kubernetes/v4.4.0/schema.json#/resources/kubernetes:storage.k8s.io%2Fv1:StorageClass" to "/kubernetes/v4.18.3/schema.json#/resources/kubernetes:storage.k8s.io%2Fv1:StorageClass"🟡"provider" type changed from "/aws/v6.18.2/schema.json#/provider" to "/aws/v6.65.0/schema.json#/provider"🟡"role" type changed from "/aws/v6.18.2/schema.json#/resources/aws:iam%2Frole:Role" to "/aws/v6.65.0/schema.json#/resources/aws:iam%2Frole:Role"🟡"eks:index:FargateProfile": properties: "selectors": items type changed from "/aws/v6.18.2/schema.json#/types/aws:eks%2FFargateProfileSelector:FargateProfileSelector" to "/aws/v6.65.0/schema.json#/types/aws:eks%2FFargateProfileSelector:FargateProfileSelector"🟡"autoScalingGroup" type changed from "/aws/v6.18.2/schema.json#/resources/aws:autoscaling%2Fgroup:Group" to "/aws/v6.65.0/schema.json#/resources/aws:autoscaling%2Fgroup:Group"🟡"extraNodeSecurityGroups": items type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup"🟡"nodeSecurityGroup" type changed from "/aws/v6.18.2/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup" to "/aws/v6.65.0/schema.json#/resources/aws:ec2%2FsecurityGroup:SecurityGroup"🟡"eks:index:StorageClass": properties: "metadata" type changed from "/kubernetes/v4.4.0/schema.json#/types/kubernetes:meta%2Fv1:ObjectMeta" to "/kubernetes/v4.18.3/schema.json#/types/kubernetes:meta%2Fv1:ObjectMeta"No new resources/functions.
What's Changed
Full Changelog: v3.4.0...v3.5.0
v3.4.0Compare Source
Does the PR have any schema changes?
Looking good! No breaking changes found.
No new resources/functions.
What's Changed
Full Changelog: v3.3.0...v3.4.0
v3.3.0Compare Source
Does the PR have any schema changes?
Looking good! No breaking changes found.
No new resources/functions.
What's Changed
New Contributors
Full Changelog: v3.2.0...v3.3.0
v3.2.0Compare Source
Does the PR have any schema changes?
Looking good! No breaking changes found.
No new resources/functions.
What's Changed
Full Changelog: v3.1.0...v3.2.0
v3.1.0Compare Source
Does the PR have any schema changes?
Looking good! No breaking changes found.
No new resources/functions.
What's Changed
./testsby @blampe in https://github.com/pulumi/pulumi-eks/pull/1490Full Changelog: v3.0.2...v3.1.0
v3.0.2Compare Source
Does the PR have any schema changes?
Looking good! No breaking changes found.
No new resources/functions.
What's Changed
Full Changelog: v3.0.1...v3.0.2
v3.0.1Compare Source
Does the PR have any schema changes?
Looking good! No breaking changes found.
No new resources/functions.
What's Changed
Full Changelog: v3.0.0...v3.0.1
v3.0.0Compare Source
This is the 3.0.0 major release (see #1425).
This release delivers significant improvements in flexibility, security and introduces new features to enhance your Kubernetes experience on AWS.
AWS recently announced the deprecation of two features used by default in Pulumi EKS: the aws-auth ConfigMap and the AL2 operating system. Pulumi EKS v3 addresses these deprecations, enhances the maintainability of the provider, and aligns it with EKS best practices.
Key Highlights of EKS V3
Support for Amazon Linux 2023 (AL2023) and Bottlerocket Operating Systems: Enhanced operating system options for node groups, allowing you to choose the OS that best fits your workloads and compliance needs. This addresses the upcoming deprecation of Amazon Linux 2 (AL2).
Access Entries for IAM Integration: Enables replacement of the deprecated aws-auth ConfigMap with Access Entries for managing Kubernetes authentication.
EKS Managed Addons: Simplified management of
vpc-cni,coredns, andkube-proxyas EKS managed addons.EKS Security Groups for Pods and Network Policies: Enhanced network security and control within EKS clusters.
New Features and Improvements
Support for Amazon Linux 2023 and Bottlerocket
We have expanded the operating system options for node groups in EKS v3 to address the upcoming deprecation of Amazon Linux 2 (AL2). You can now choose between Amazon Linux 2 (deprecated), Amazon Linux 2023 and Bottlerocket for your EKS nodes. This flexibility allows you to select the OS that best fits your workloads, security requirements, and compliance needs, while ensuring you are using a supported and actively maintained operating system. We've introduced a new
operatingSystemproperty for node groups to facilitate this choice.Access Entries for IAM Integration
AWS has introduced Access Entries as a new method for granting IAM principals access to Kubernetes resources. This approach relies solely on AWS resources for managing Kubernetes auth, replacing the deprecated
aws-authConfigMap. You can now leverage Access Entries by setting theauthenticationModetoAPIin your cluster configuration.EKS Managed Addons
The EKS cluster components
vpc-cni,coredns, andkube-proxyare now configured as EKS managed addons. This change simplifies management, especially for clusters with private API endpoints, and ensures that these critical components stay up to date automatically. Additionally it removes the dependency onkubectl, allowing pulumi-native management of clusters.Cluster Autoscaler Integration
Pulumi EKS v3 introduces better support for the Kubernetes Cluster Autoscaler. A new
ignoreScalingChangesparameter for node groups allows Pulumi to ignore external scaling changes, facilitating seamless integration with dynamic scaling solutions.EKS Security Groups for Pods and Network Policies
We've added support for EKS security groups for pods (example) and EKS Network Policies (example), providing more granular control over pod-to-pod and pod-to-external network communication within your EKS clusters.
Migration Guide
To help you transition smoothly, we've prepared a migration guide with these key steps:
NodeGroupcomponent withNodeGroupV2.Please refer to our EKS v3 Migration Documentation for a detailed guide.
Full Changelog: v2.8.1...v3.0.0
v3.0.0-beta.2Compare Source
What's Changed
Full Changelog: v3.0.0-beta.1...v3.0.0-beta.2
v3.0.0-beta.1Compare Source
What's Changed
skipDefaultNodeGroupis enabled by @flostadler in https://github.com/pulumi/pulumi-eks/pull/1411Full Changelog: v3.0.0-alpha.8...v3.0.0-beta.1
v3.0.0-alpha.8Compare Source
What's Changed
Full Changelog: v3.0.0-alpha.7...v3.0.0-alpha.8
v3.0.0-alpha.7Compare Source
pulumi/actions (pulumi/actions)
v6Compare Source
pulumi/pulumi-package-publisher (pulumi/pulumi-package-publisher)
v0.0.21Compare Source
What's Changed
New Contributors
Full Changelog: pulumi/pulumi-package-publisher@v0.0.20...v0.0.21
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "every weekday" (UTC).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.