logo

Remove failed node in TKG after MachineHealth checks mark it failed

With Tanzu Kubernetes Grid Cluster API implements Machine Health-Check that provides node health monitoring and node auto-repair for Tanzu Kubernetes clusters.

In action, what happens is it automatically consolidates the desired state with regards to node configuration in the event of failure. Saw this in action when power wen-out and caused one my worker nodes to be corrupted.

As a response, the cluster-api provisioned a new node to reach the desired state of the kubernetes cluster. At the same time, it would try to recover the failed node by powering on the VM.

Here is the kubernetes cluster status after Tanzu automatically provisioned a new node to compensate for the failed node.

In my case, the failed node is unrecoverable so the only way to move clean it up is to remove it. To do this, issue the following:

kubectl delete node <node name>

View Post

After the operation, ClusterAPI will also delete the VM object from vCenter.

Hope that helps.

Enjoy!

  1. John1246 Reply
  2. Ellie3587 Reply
  3. Cornelius4020 Reply
  4. Harry3140 Reply
  5. Brayden3679 Reply
  6. Walter588 Reply
  7. Madeleine490 Reply
  8. Josephine4968 Reply
  9. Clarence4077 Reply
  10. Tom2891 Reply
  11. Ryan2598 Reply
  12. Drake4047 Reply
  13. nhà cái 66b Reply

    Nhiều người vẫn hiểu lầm rằng tất cả các trang nhà cái đổi thưởng đều là cờ bạc trá hình và bất hợp pháp. Thực tế, slot365 hoạt động dưới sự giám sát của các tổ chức cấp phép uy tín trong ngành iGaming quốc tế. Nền tảng này tuân thủ nghiêm ngặt các quy định về chống rửa tiền, bảo vệ người chơi và chơi game có trách nhiệm.

  14. Mariah2464 Reply
  15. Lily771 Reply
  16. Ruby4421 Reply
  17. Lacey1756 Reply
  18. Tony1356 Reply
  19. Keegan2357 Reply
  20. Lola625 Reply

Leave a Reply

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.