Skip to content

Latest commit

 

History

History
23 lines (16 loc) · 858 Bytes

troubleshooting.md

File metadata and controls

23 lines (16 loc) · 858 Bytes

Troubleshooting

  • If a Stack is stuck due to conflicting updates from a previous failed run, you'll need to manually unlock the stack. You can attach and use the stack's pod to run other commands.

    kubectl exec --stdin --tty my-stack-0q4s6z9z
pulumi cancel -y

  • If your Stack CR encounters an error and is not processed, the operator by will still continue to deploy reconciliation loops until a successful update is reached.

    In these cases it's best to delete the Stack CR and redeploy it.

    If destroyOnFinalize: true is set, you first have to remove its finalizer before the Stack CR can be deleted.

    e.g.

    kubectl patch stack my-stack-0q4s6z9z -p '{"metadata":{"finalizers": []}}' --type=merge