<p>I upgraded the elasticsearch chart in kubernetes from 6.6 to 7.10.2 version. Data and master pods are running and ready but, the clients aren't ready (2 clients, 2 data , 3 master).</p>
<p>This is their status:</p>
<pre><code>NAME                                    READY   STATUS    RESTARTS   AGE

    elasticsearch-client-685c875bb5-5mcxg   0/1     Running   0          2m23s
    elasticsearch-client-685c875bb5-cs9lq   0/1     Running     0          24m
</code></pre>
<p>When I run describe I see this warning:</p>
<pre><code>  Warning  Unhealthy  10s (x10 over 100s)  kubelet,  Readiness probe failed: Get http://_cluster/health: net/http: request canceled (Client. Timeout exceeded while awaiting headers)
</code></pre>
<p>and in kubectl logs, I get this</p>
<pre><code>{&quot;type&quot;: &quot;server&quot;, &quot;timestamp&quot;: &quot;2021-01-24T13:43:41,318Z&quot;, &quot;level&quot;: &quot;WARN&quot;, &quot;component&quot;: &quot;r.suppressed&quot;, &quot;cluster.name&quot;: &quot;elasticsearch&quot;, &quot;node.name&quot;: &quot;elasticsearch-client-685c875bb5-5mcxg&quot;, &quot;message&quot;: &quot;path: /_cluster/health, params: {}&quot;,
&quot;stacktrace&quot;: [&quot;org.elasticsearch.discovery.MasterNotDiscoveredException: null&quot;,
&quot;at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$2.onTimeout(TransportMasterNodeAction.java:230) [elasticsearch-7.10.2.jar:7.10.2]&quot;,
&quot;at org.elasticsearch.cluster.ClusterStateObserver$ContextPreservingListener.onTimeout(ClusterStateObserver.java:335) [elasticsearch-7.10.2.jar:7.10.2]&quot;,
&quot;at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:252) [elasticsearch-7.10.2.jar:7.10.2]&quot;,
&quot;at org.elasticsearch.cluster.service.ClusterApplierService$NotifyTimeout.run(ClusterApplierService.java:601) [elasticsearch-7.10.2.jar:7.10.2]&quot;,
&quot;at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:684) [elasticsearch-7.10.2.jar:7.10.2]&quot;,
&quot;at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) [?:?]&quot;,
&quot;at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) [?:?]&quot;,
&quot;at java.lang.Thread.run(Thread.java:832) [?:?]&quot;] }
{&quot;type&quot;: &quot;server&quot;, &quot;timestamp&quot;: &quot;2021-01-24T13:43:51,319Z&quot;, &quot;level&quot;: &quot;WARN&quot;, &quot;component&quot;: &quot;r.suppressed&quot;, &quot;cluster.name&quot;: &quot;elasticsearch&quot;, &quot;node.name&quot;: &quot;elasticsearch-client-685c875bb5-5mcxg&quot;, &quot;message&quot;: &quot;path: /_cluster/health, params: {}&quot;,
&quot;stacktrace&quot;: [&quot;org.elasticsearch.discovery.MasterNotDiscoveredException: null&quot;,
&quot;at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$2.onTimeout(TransportMasterNodeAction.java:230) [elasticsearch-7.10.2.jar:7.10.2]&quot;,
&quot;at org.elasticsearch.cluster.ClusterStateObserver$ContextPreservingListener.onTimeout(ClusterStateObserver.java:335) [elasticsearch-7.10.2.jar:7.10.2]&quot;,
&quot;at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:252) [elasticsearch-7.10.2.jar:7.10.2]&quot;,
&quot;at org.elasticsearch.cluster.service.ClusterApplierService$NotifyTimeout.run(ClusterApplierService.java:601) [elasticsearch-7.10.2.jar:7.10.2]&quot;,
&quot;at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:684) [elasticsearch-7.10.2.jar:7.10.2]&quot;,
&quot;at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) [?:?]&quot;,
&quot;at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) [?:?]&quot;,
&quot;at java.lang.Thread.run(Thread.java:832) [?:?]&quot;] }
</code></pre>
<p>I set the readiness and liveness initialDelaySeconds to 90
what might be the problem here?</p>

NoamiA
<p>Since you have upgraded from 6.x to 7.x, make sure that you have set <code>cluster.initial_master_nodes</code> in your <code>env</code> or in the <code>elasticsearch.yml</code> config file.</p>
