unknown resource type NodeGroupV2
See original GitHub issueWhat happened?
Using Pulumi EKS 0.42.1 in Go to provision a NodeGroup using NodeGroupV2, it encounter this error:
Diagnostics:
pulumi:pulumi:Stack (eks-vboulineau-eks-test):
Error: unknown resource type eks:index:NodeGroupV2: Error: unknown resource type eks:index:NodeGroupV2
at unknownResourceRejectedPromise (/Users/vincent.boulineau/.pulumi/plugins/resource-eks-v0.42.1/node_modules/@pulumi/cmd/provider/index.ts:145:27)
at Provider.construct (/Users/vincent.boulineau/.pulumi/plugins/resource-eks-v0.42.1/node_modules/@pulumi/cmd/provider/index.ts:124:15)
at Server.<anonymous> (/Users/vincent.boulineau/.pulumi/plugins/resource-eks-v0.42.1/node_modules/@pulumi/provider/server.ts:326:48)
at Generator.next (<anonymous>)
at fulfilled (/Users/vincent.boulineau/.pulumi/plugins/resource-eks-v0.42.1/node_modules/@pulumi/pulumi/provider/server.js:18:58)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
error: an unhandled error occurred: program failed:
waiting for RPCs: rpc error: code = Unknown desc = unknown resource type eks:index:NodeGroupV2
Steps to reproduce
Create a cluster with a NodeGroupV2. Sample Go code:
return eks.NewNodeGroupV2(e.Ctx, "test-cluster", &eks.NodeGroupV2Args{
Cluster: cluster.Core,
DesiredCapacity: pulumi.Int(1),
KeyName: pulumi.StringPtr(e.DefaultKeyPairName()),
AmiId: ami,
InstanceType: instanceType,
NodeRootVolumeSize: pulumi.Int(80),
NodeAssociatePublicIpAddress: pulumi.BoolPtr(false),
InstanceProfile: instanceProfile,
})
The imports:
awsEks "github.com/pulumi/pulumi-aws/sdk/v5/go/aws/eks"
awsIam "github.com/pulumi/pulumi-aws/sdk/v5/go/aws/iam"
"github.com/pulumi/pulumi-aws/sdk/v5/go/aws/ssm"
"github.com/pulumi/pulumi-eks/sdk/go/eks"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
Expected Behavior
NodeGroup is provisioned
Actual Behavior
Error is returned
Output of pulumi about
❯ pulumi about
CLI
Version 3.40.2
Go Version go1.19.1
Go Compiler gc
Plugins
NAME VERSION
aws 5.7.2
awsx 1.0.0-beta.11
docker 3.2.0
eks 0.42.1
go unknown
kubernetes 3.21.4
Host
OS darwin
Version 12.6
Arch x86_64
This project is written in go: executable='/usr/local/bin/go' version='go version go1.19.1 darwin/amd64'
Backend
Name laptop
URL gs://vboulineau-pulumi-test
User vincent.boulineau
Organizations
Dependencies:
NAME VERSION
github.com/pulumi/pulumi-aws/sdk/v5 5.7.2
github.com/pulumi/pulumi-awsx/sdk 1.0.0-beta.11
github.com/pulumi/pulumi-eks/sdk 0.42.1
github.com/pulumi/pulumi/sdk/v3 3.40.1
Pulumi locates its logs in /var/folders/h4/xp6zgrvd5_32n33jl3v53wt00000gn/T/ by default
warning: Failed to get information about the current stack: No current stack
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you’ve opened one already).
Issue Analytics
- State:
- Created a year ago
- Comments:13 (8 by maintainers)
Top Results From Across the Web
Better error reporting when resource is not known · Issue #1642
When an unknown resource type is passed to an eksctl command the error is misleading. For example: $ eksctl get yaddayadda --region ap-northeast ......
Read more >Puppet Evaluation Error. Error while evaluating a Resource ...
The module that provides the referred Unknown resource type is not available where your Puppet code is compiled. Find the module you need...
Read more >Puppet standalone error - Unknown resource type
Solution A: Call testme_service::install a different way in profile. profile/manifests/init.pp. class profile::testme_service { class ...
Read more >Problems with the use of custom types - Google Groups
I add the module to a client and start a puppetrun there. I see the custom type being synced, but after that I...
Read more >[Puppet Users] Unknown resource type after Upgrade
Hey folks, I am currently upgrading to 6.x on a test setup using my live puppet code; trying to get it to work...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

A fix for this is in the process of being released - with the version 0.42.2 - hopefully complete within the hour.
I am facing the same thing but with python - I am sure I have imported the correct version and the code sample is taken from pulumi-eks repo example
`
The error I faced is -
Is there no first class python support at the moment for NodegroupV2 ? Or is this is bug ?