Failed deployments are not tainted

[vladimirtiukhtin]

Terraform Version, Provider Version and Kubernetes Version

Terraform v1.6.2
on linux_amd64
+ provider registry.terraform.io/hashicorp/kubernetes v2.23.0

Affected Resource(s)

• kubernetes_deployment_v1

Steps to Reproduce

I am seeing strange behavior where on first run existing deployment gets updated with an invalid image address, it expectedly fails with

Error: Waiting for rollout to finish: 1 old replicas are pending termination

But second run completes with success because "no changes". Deployment though still runs old version as kubernetes stopped roll out

Expected Behavior

I expected to see a taint on failing resource

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[BBBmau]

@vladimirtiukhtin Hello! Thank you for opening this issue, could you provide a tfconfig so that we can reproduce this issue?

[iBrandyJackson]

Without further feedback to proceed, we're closing this ticket to maintain clarity in our issue tracker. This closure is purely procedural; we're still interested in addressing your concerns.

Should this issue persist or if you have additional information to share, please feel free to open a new ticket. Your contributions are valuable to us, and we're keen to assist wherever possible.