-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow all arguments in NodeGroupV2 to be pulumi.Input
#1274
Comments
As an aside, I did try to do this myself so I could PR it, but unfortunately hit some serialisation issues that I'm not familiar enough with to debug effectively. |
Thank you for trying to send a PR here! Unfortunately it's a little more involved. Our team will have a look at this when planning the next major release, possibly combined with #603 |
CC @flostadler |
Historically the following `NodeGroup` & `NodeGroupV2` input properties have been plain: - `kubeletExtraArgs` - `bootstrapExtraArgs` - `labels` - `taints` - `nodeAssociatePublicIpAddress` Those should instead be inputs so users can pass outputs into them. fixes #1274
We've addressed this as part of #1415. This will be released with EKS v3 |
Added to epic https://github.com/pulumi/home/issues/3558 |
Hello!
Issue details
I ran into an issue today when trying to create a NodeGroup whose labels and taints were not known initially and were therefore
pulumi.Output
's. Unfortunately, thelabels
andtaints
args (and a few more) in theNodeGroupV2
component are treated and typed as plain values, so it isn't possible to use potentially-unresolved values when creating them.Please add support for
labels
andtaints
to be resolved frompulumi.Output
.Affected area/feature
This component.
The text was updated successfully, but these errors were encountered: