# Impact If Worker Node Goes Down Where 'calico-kube-controllers', 'metrics-server', 'dashboard-metric

## Problem

What will be impact if worker node goes down where the below pods are running:

* calico-kube-controllers
* metrics-server-v0.5.0
* dashboard-metrics-scraper
* kubernetes-dashboard

## Environment

* Platform9 Managed Kubernetes - v5.1 and Higher

## Answer

**calico-kube-controllers:**

* Outside of calico being unable to sync any changes to the pod or namespace objects to apply policies, etc. would be impacted the most when the calico kube controller goes down.
* Garbage collects IP addresses. Automatically provisions host endpoints for Kubernetes nodes (from: <https://projectcalico.docs.tigera.io/reference/kube-controllers/configuration>)

**kubernetes-dashboard** and **dashboard-metrics-scraper**:

* The kubernetes dashboard will be unavailable in the first case
* The dashboard will not have the basic metrics that it usually displays.

**metrics-server-v0.5.0:**

* horizontal pod autoscalers
* vertical pod autoscalers
* `kubectl top` commands won't work.

## Additional Information

These pods can be configured high availability mode by increasing the replicas.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://platform9.com/kb/pmk/frequently-asked-questions/impact-if-worker-node-goes-down-where-calico-kube-controllers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.