blue-nail-2918
10/24/2024, 10:24 AMfrom pulumi_aws.eks import NodeGroup, NodeGroupLaunchTemplateArgs
return NodeGroup(
resource_name=name.replace("-","_").lower(),
cluster_name=eks_cluster_name,
launch_template=NodeGroupLaunchTemplateArgs(
id=launch_template.id,
version=launch_template.latest_version,
),
node_group_name=name,
node_role_arn=self.nodegroup_iam_role_resource.arn,
scaling_config={
"desiredSize": desired_nodes,
"maxSize": max_nodes,
"minSize": min_nodes,
},
subnet_ids=available_subnets,
tags = {
"key1": "Value1",
"key2": "Value2",
},
update_config={
"maxUnavailable": unavailable_nodes,
},
opts=ResourceOptions(depends_on=[launch_template]),
)
blue-nail-2918
10/24/2024, 11:40 AMLaunchTemplate
resource in my deployment was mis-configured.
I've set this resource tag_specifications=[LaunchTemplateTagSpecificationArgs(tags....
in a bad way where I've tried to set a tag value using my EKS cluster resource .name
method and append it (this is an Output object actually which cannot be manipulated as a str
But Pulumi instead of providing its common exception about Output
object mis-usage this time did not... and also it pointed the issue to the NodeGroup
resource instead of the LaunchTemplate
one....
Once I've sort that resource name as string - everything working as it was supposed to.No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.
Powered by