No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

You might be able to `pulumi refresh`. If not, you can use `pulumi state delete` to delete the resource by its URN.

``` Attempting to deploy or update resources with 1 pending operations from previous deployment.
      * urn:pulumi:abfa-public-site-dev::wishbone::assemble:aws_apple:EKS$hybrid-cloud:aws/eks:ControlPlane$aws:eks/cluster:Cluster::abfa-public-site-dev-control-cluster, interrupted while deleting
    These resources are in an unknown state because the Pulumi CLI was interrupted while waiting for changes to these resources to complete. You should confirm whether or not the operations listed completed successfully by checking the state of the appropriate provider. For example, if you are using AWS, you can confirm using the AWS Console.
    
    Once you have confirmed the status of the interrupted operations, you can repair your stack using `pulumi refresh` which will refresh the state from the provider you are using and clear the pending operations if there are any.
    
    Note that `pulumi refresh` will need to be run interactively to clear pending CREATE operations.
    error: update failed
 
  aws:eks:Cluster (abfa-public-site-dev-control-cluster):
    error: pre-step event returned an error: failed to verify snapshot: resource urn:pulumi:abfa-public-site-dev::wishbone::assemble:aws_apple:EKS$hybrid-cloud:aws/eks:ControlPlane$aws:eks/cluster:Cluster$pulumi:providers:kubernetes$kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRole::abfa-public-site-dev-control-restricted-psp-clusterrole|rbac.authorization.k8s.io/v1:ClusterRole::abfa-public-site-dev-control-restricted-psp-clusterrole> refers to unknown provider urn:pulumi:abfa-public-site-dev::wishbone::assemble:aws_apple:EKS$hybrid-cloud:aws/eks:ControlPlane$aws:eks/cluster:Cluster$pulumi:providers:kubernetes::abfa-public-site-dev-control-eks-k8s::ebb23712-8ce2-4f98-8915-fc26ebe56095```

The error is very informative. You can repair your stack and refresh it to get everything back the way it should be.

Step 1:
&gt;  You should confirm whether or not the operations listed completed successfully by checking the state of the appropriate provider. For example, if you are using AWS, you can confirm using the AWS Console.
Step 2:
&gt; Once you have confirmed the status of the interrupted operations, you can repair your stack using `pulumi refresh` which will refresh the state from the provider you are using and clear the pending operations if there are any.
