most-pager-3805603/23/2019, 7:01 AM
. After recreating the cluster, i started to see the following error message regularly:
The error is inconsistent and when it happens, a new cluster is created and the previous one is marked to be deleted, what shouldn’t be possible because it has the flag
kubernetes:core:ConfigMap (api-config-map): warning: The provider for this resource has inputs that are not known during preview. This preview may not correctly represent the changes that will be applied during an update.
. The k8s resources from the previous cluster are moved to the new cluster instantly, but they’re not created in the new cluster actually. Also, to make any updates to the stack, the previous cluster needs to be deleted. I’m not sure what is happening. Any ideas?
package, i literally had the same issue. Another cluster that is running this same version
version is working properly. Both clusters are using the same Pulumi version (17.2).
creamy-potato-2940203/23/2019, 5:04 PM
stocky-spoon-2890303/23/2019, 6:07 PM
most-pager-3805603/23/2019, 6:32 PM
and i had no issues after more than 10 deployments.
What it looks like is that Pulumi is having issues to get the information about the cluster, so it assumes that the cluster has a specific configuration, ignoring that fact it’s protected and triggering unnecessary changes.Is that possible? I believe the main issue here is how Pulumi behaved in that situation. Assuming a specific resource configuration can lead to a lot of unexpected results and it makes much more difficult to understand what’s really happening.
most-pager-3805603/25/2019, 8:26 PM