# ECK Cluster in yellow state but cluster is green **URL:** \ **Category:** Elastic Cloud on Kubernetes (ECK)\ **Created:** [December 30, 2021, 8:58am UTC](https://discuss.elastic.co/t/eck-cluster-in-yellow-state-but-cluster-is-green/293185 "2021-12-30T08:58:53Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![julien.couturier](https://avatars.discourse-cdn.com/v4/letter/j/4491bb/32.png) [@julien.couturier](https://discuss.elastic.co/u/julien.couturier)\ **Post date:** [December 30, 2021, 8:58am UTC](https://discuss.elastic.co/t/eck-cluster-in-yellow-state-but-cluster-is-green/293185/1 "2021-12-30T08:58:54Z")
Hi, My Elastic stack is working well but I discovered that the ECK status was "Yellow" when I tried to upgrade to 7.16.2. kubectl get es NAME HEALTH NODES VERSION PHASE AGE tbb-es yellow 3 7.11.2 Ready 34d But when I check my ES Cluster health, everything is right : `GET _cluster/health` ```json { "cluster_name" : "tbb-es", "status" : "green", "timed_out" : false, "number_of_nodes" : 3, "number_of_data_nodes" : 3, "active_primary_shards" : 312, "active_shards" : 761, "relocating_shards" : 0, "initializing_shards" : 0, "unassigned_shards" : 0, "delayed_unassigned_shards" : 0, "number_of_pending_tasks" : 0, "number_of_in_flight_fetch" : 0, "task_max_waiting_in_queue_millis" : 0, "active_shards_percent_as_number" : 100.0 } ``` `GET _cat/allocation?v` shards disk.indices disk.used disk.avail disk.total disk.percent host ip node 253 154.1gb 154.9gb 40.9gb 195.8gb 79 10.2.1.10 10.2.1.10 tbb-es-es-default-2 254 137.7gb 139gb 56.7gb 195.8gb 71 10.2.0.28 10.2.0.28 tbb-es-es-default-0 254 155.2gb 156.5gb 39.2gb 195.8gb 79 10.2.2.8 10.2.2.8 tbb-es-es-default-1 `GET _cluster/settings` ```json { "persistent" : { }, "transient" : { "cluster" : { "routing" : { "allocation" : { "enable" : "all", "exclude" : { "_name" : "none_excluded" } } } } } } ``` ECK version is 1.4.0 My update strategy seems good : Update Strategy: Change Budget: Max Surge: 1 Max Unavailable: 1 What can explain this yellow status ? ---
**Author:** ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)\ **Post date:** [January 6, 2022, 1:57pm UTC](https://discuss.elastic.co/t/eck-cluster-in-yellow-state-but-cluster-is-green/293185/2 "2022-01-06T13:57:04Z")
> [@julien.couturier](#): > > What can explain this yellow status ? Could you check the operator logs to see if there is something preventing the operator to get/update the status ? Thanks ---
**Author:** ![julien.couturier](https://avatars.discourse-cdn.com/v4/letter/j/4491bb/32.png) [@julien.couturier](https://discuss.elastic.co/u/julien.couturier)\ **Post date:** [January 6, 2022, 5:00pm UTC](https://discuss.elastic.co/t/eck-cluster-in-yellow-state-but-cluster-is-green/293185/3 "2022-01-06T17:00:13Z")
I already checked the operator logs but I did not find anything significant. But, on Tuesday I upgraded my kubernetes environment so it was needed to restart all deployments. After this rollup restart, the ECK cluster became Green and started to upgrade itself. I suppose, a simple rollup restart would have solved my issue too. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 3, 2022, 5:00pm UTC](https://discuss.elastic.co/t/eck-cluster-in-yellow-state-but-cluster-is-green/293185/4 "2022-02-03T17:00:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.