Closed mhamann closed 1 year ago
Hi @mhamann, sorry you're running into trouble here. It's surprising that it happens when retrieving schema information which is a common functionality. Can you confirm that you are still able to perform other Pulumi operations on the cluster, such as other changes or refresh
?
Also, this page describes how to obtain a more verbose log. It would be great if you could attach that, but check first for things you wouldn't like to post in public. Alternatively, you could try to check the log for that API response that cannot be parsed.
Closing due to inactivity
What happened?
I have an EKS cluster running k8s 1.21.4. It's been managed by Pulumi for over a year with various config changes over time. Today, when attempting to add an additional role mapping to the cluster config, the
pulumi up
preview step works fine, but when selecting "yes" to apply the changes, the following error occurs:Expected Behavior
No error should be thrown, because Pulumi successfully parsed whatever it needed to in order to connect to the cluster.
Steps to reproduce
Create an EKS cluster in the following manner:
Now add an additional role mapping:
Output of
pulumi about
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).