(aws-eks): It seems impossible to add Fargate profile to an existing EKS cluster due to ICluster/Cluster argument mismatch

[vgribok]

To get a reference to an existing cluster, one has to use Cluster.FromClusterAttributes() returning ICluster.
To add a Fargate profile one needs to supply Cluster and not ICluster, to either Cluster.AddFargateProfile() or to new FargateProfileProps {}.

Reproduction Steps

See above.

What did you expect to happen?

To be able to combine usage of Cluster.FromClusterAttributes() to find an existing EKS cluster, and cluster.AddFargateProfile() to add Fargate to it.

Ability to add Fargate profile to an existing EKS cluster.

What actually happened?

Can't pass ICluster typed variable returned by Cluster.FromClusterAttributes() to either Cluster.AddFargateProfile() or to new FargateProfileProps {}.

Environment

• CDK CLI Version : 1.92.0
• Framework Version: 1.92.0
• Node.js Version: v15.5.0
• OS : Windows 10 20H2
• Language (Version): all

Other

Related to #13153

---

This is 🐛 Bug Report

[peterwoodworth]

Thank you for the concern, but I don't think this is a bug. By design, imported resources cannot be modified.

You're going to have to find another way to do what you are currently trying to accomplish, which is what the guidance issue you linked is for! I've still been keeping an eye on it, but I've been unable to find the time to help figure out a workaround. It is something I have been trying to get back to, and I should respond within the next week or so

[vgribok]

Thank you for the concern, but I don't think this is a bug. By design, imported resources cannot be modified.

I didn't realize that, thank you, @peterwoodworth. That's unfortunate though: if I can add a K8s namespace to an existing EKS cluster via CDK, not being able to add corresponding Fargate profile for that namespace makes no sense as it pretty much prohibits using all-fargate EKS clusters with CDK after cluster creation.

[peterwoodworth]

@vgribok yeah it is unfortunate :/

I'm going to close this issue and move our discussion back over to the guidance issue #13153. I will try to help you guys out by the end of next week, as this will take me some time 😛

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.