ancient-megabyte-7958801/26/2021, 6:57 PM
doesn't work to bring the stack into sync with the cluster.
The concerning thing is that these resources were removed by the pulumi script, but the script failed in a latter part of the execution (couldn't get ip address property from
object), and so the stack is now out of sync with what the script removed, and I can't get the stack back in sync.
the stack since there are things in place that would be very problematic to re-create.
gentle-diamond-7014701/26/2021, 6:59 PM
ancient-megabyte-7958801/26/2021, 7:08 PM
inspects the stack and the script, and tries to bring them together. So if the app doesn't have a resource described, and the cluster doesn't have it, but the stack does have that resource, it would remove it from the stack.
to fix that.
gentle-diamond-7014701/26/2021, 8:46 PM
to fix that too.
To expand a bit on the behavior you described... if you have a resource in your Pulumi state, but that resource does not exist in your provider,
should "fix" that, meaning recognize the resource no longer exists and remove from your state file.
resource itself is a component resource in Pulumi's terms, so it does not exist in that exact form in your k8s cluster.
should have removed any of the sub-resources of that chart (if they no longer existed), but the chart component might not be removed. I'll need to confirm the "component refresh" behavior with a Pulumi engineer.
ancient-megabyte-7958801/26/2021, 10:32 PM