To ease the impact of the breaking API changes caused by generating the node SDK, we decided to add additional scalar inputs that simplify UX across all SDKs (for more details see internal doc).
This change adds the scalar properties mentioned in the doc and adds acceptance tests for them.
While adding the acceptance tests I noticed that running pods on Fargate doesn't work deterministically. In some cases the cluster fails to get healthy (coredns stuck in pending).
This was caused by a race-condition between coredns starting and the fargate profile being created. If the fargate profile deployed after coredns, the pods got stuck in pending because they got assigned to the default-scheduler instead of the fargate-scheduler.
The fix is relatively easy; making coredns depend on the fargate profile.
The only useful property of the default node group is the auto scaling group. Exposing its name allows users to reference it in IAM roles, tags, etc. Default to ””
Arn and Url are properties needed to set up IAM identities for pods (required for the assume role policy of the IAM role). Users currently need to trim the https:// part of the url to actually use it. We should expose oidcProvider with that already done to ease usage.
To ease the impact of the breaking API changes caused by generating the node SDK, we decided to add additional scalar inputs that simplify UX across all SDKs (for more details see internal doc).
This change adds the scalar properties mentioned in the doc and adds acceptance tests for them. While adding the acceptance tests I noticed that running pods on Fargate doesn't work deterministically. In some cases the cluster fails to get healthy (coredns stuck in pending). This was caused by a race-condition between coredns starting and the fargate profile being created. If the fargate profile deployed after coredns, the pods got stuck in pending because they got assigned to the
default-scheduler
instead of thefargate-scheduler
. The fix is relatively easy; making coredns depend on the fargate profile.I'll separately update the migration guide.
New properties
clusterSecurityGroup: Output<aws.ec2.SecurityGroup \| undefined>
clusterSecurityGroupId: Output<string>
the EKS created security group id
nodeSecurityGroup: Output<aws.ec2.SecurityGroup \| undefined>
nodeSecurityGroupId: Output<string>
eksClusterIngressRule: Output<aws.ec2.SecurityGroupRule \| undefined>
clusterIngressRuleId: Output<string>
””
defaultNodeGroup: Output<eks.NodeGroupData \| undefined>
defaultNodeGroupAsgName: Output<string>
””
core
fargateProfile: Output<aws.eks.FargateProfile \| undefined>
fargateProfileId: Output<string>
””
fargateProfileStatus: Output<string>
””
oidcProvider: Output<aws.iam.OpenIdConnectProvider \| undefined>
oidcProviderArn: Output<string>
&oidcProviderUrl: Output<string>
&oidcIssuer: Output<string
https://
part of the url to actually use it. We should exposeoidcProvider
with that already done to ease usage.Fixes https://github.com/pulumi/pulumi-eks/issues/1041