Skip to content
This repository has been archived by the owner on Oct 10, 2023. It is now read-only.

Tkr resolver blocks cluster update even when cluster is marked for deletion #2543

Closed
9 tasks
nehagjain15 opened this issue Jun 3, 2022 · 1 comment · Fixed by #2545
Closed
9 tasks

Tkr resolver blocks cluster update even when cluster is marked for deletion #2543

nehagjain15 opened this issue Jun 3, 2022 · 1 comment · Fixed by #2545
Assignees

Comments

@nehagjain15
Copy link

Bug description
A cluster is stuck in deleting state. If we try to manually edit the cluster and remove the finalizer which is blocking deletion, patch is denied by TKr resolver webhook.

Affected product area (please put an X in all that apply)

  • [x ] APIs
  • Addons
  • CLI
  • Docs
  • IAM
  • Installation
  • Plugin
  • Security
  • Test and Release
  • User Experience

Expected behavior
If a Cluster is marked for deletion, TKr resolver webhook should not block any update to cluster.
Steps to reproduce the bug

Version (include the SHA if the version is not obvious)

Environment where the bug was observed (cloud, OS, etc)
vSphere Environment

Relevant Debug Output (Logs, manifests, etc)

You can run `kubectl replace -f /tmp/kubectl-edit-3118235449.yaml` to try this update again.
@nehagjain15 nehagjain15 added kind/bug PR/Issue related to a bug needs-triage Indicates an issue or PR needs to be triaged labels Jun 3, 2022
@github-actions
Copy link

github-actions bot commented Jun 3, 2022

Hey @nehagjain15! Thanks for opening your first issue. We appreciate your contribution and welcome you to our community! We are glad to have you here and to have your input on Tanzu Framework.

@imikushin imikushin self-assigned this Jun 3, 2022
@imikushin imikushin added area/api area/tkr priority/critical-urgent and removed needs-triage Indicates an issue or PR needs to be triaged labels Jun 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants