<p>I am somewhat brand-new to Kubernetes.</p>
<p>I have a pod that keeps restarting, and my error is:</p>
<pre><code>    at KibanaTransport.request (/usr/share/kibana/node_modules/@elastic/transport/lib/Transport.js:524:31)
    at runMicrotasks (&lt;anonymous&gt;)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at KibanaTransport.request (/usr/share/kibana/node_modules/@kbn/core-elasticsearch-client-server-internal/target_node/create_transport.js:58:16)
    at Cluster.getSettings (/usr/share/kibana/node_modules/@elastic/elasticsearch/lib/api/api/cluster.js:157:16)
    at isInlineScriptingEnabled (/usr/share/kibana/node_modules/@kbn/core-elasticsearch-server-internal/target_node/is_scripting_enabled.js:22:20)
    at ElasticsearchService.start (/usr/share/kibana/node_modules/@kbn/core-elasticsearch-server-internal/target_node/elasticsearch_service.js:128:32)
    at Server.start (/usr/share/kibana/src/core/server/server.js:366:32)
    at Root.start (/usr/share/kibana/src/core/server/root/index.js:69:14)
    at bootstrap (/usr/share/kibana/src/core/server/bootstrap.js:120:5)
    at Command.&lt;anonymous&gt; (/usr/share/kibana/src/cli/serve/serve.js:216:5)
[2023-08-19T12:01:21.293+00:00][INFO ][plugins-system.preboot] Stopping all plugins.
[2023-08-19T12:01:21.294+00:00][INFO ][plugins-system.standard] Stopping all plugins.
[2023-08-19T12:01:21.294+00:00][INFO ][plugins.monitoring.monitoring.kibana-monitoring] Monitoring stats collection is stopped
[2023-08-19T12:01:21.297+00:00][ERROR][plugins.ruleRegistry] Error: Server is stopping; must stop all async operations
    at /usr/share/kibana/x-pack/plugins/rule_registry/server/rule_data_plugin_service/resource_installer.js:66:20
    at runMicrotasks (&lt;anonymous&gt;)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
[2023-08-19T12:01:21.298+00:00][ERROR][plugins.ruleRegistry] Error: Failure installing common resources shared between all indices. Server is stopping; must stop all async operations
    at ResourceInstaller.installWithTimeout (/usr/share/kibana/x-pack/plugins/rule_registry/server/rule_data_plugin_service/resource_installer.js:75:13)
    at runMicrotasks (&lt;anonymous&gt;)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at ResourceInstaller.installCommonResources (/usr/share/kibana/x-pack/plugins/rule_registry/server/rule_data_plugin_service/resource_installer.js:89:5)

 FATAL  TimeoutError: Request timed out 
</code></pre>
<p>The rest of my pods are running:</p>
<p><a href="https://i.stack.imgur.com/Ph0ZY.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Ph0ZY.png" alt="enter image description here" /></a></p>
<p><code>kubectl describe pod</code></p>
<p><a href="https://i.stack.imgur.com/cEfvt.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/cEfvt.png" alt="enter image description here" /></a>
What I've Tried:
Deleted the pod on its own.
Removed the deployment.
Updated the YAML file to allocate more resources and applied the changes. However, I'm uncertain if the changes were actually applied.</p>
<p>If anyone is a Kubernetes expert, I would be very appreciative if someone could provide proper guidance here.</p>
<p>Thank you.</p>

OreuhNation
<p>It's quite hard todo remote diagnostics with that amount of information. Here are basically two things that disturb me. Your Kubernetes pod running Kibana is encountering issues and keeps restarting due to errors related to communication with Elasticsearch.</p>
<p><strong>1:</strong> The &quot;Readiness probe failed: Get <a href="https://xxxxx.login" rel="nofollow noreferrer">https://xxxxx.login</a> dial tcp connect connection refused&quot; message suggests that Kibana is failing its readiness probe. A readiness probe is used to determine if a container is ready to start accepting traffic.</p>
<ul>
<li><p>Verify that the readiness probe configuration for the Kibana pod is
correct. It might be misconfigured or the service it's trying to
access (&quot;login&quot; in this case) might not be ready or available.</p>
</li>
<li><p>Check the service name, port, and path used in the readiness probe. Ensure they match the actual configuration of the application.</p>
</li>
<li><p>incease the timeout of the readiness probe</p>
</li>
</ul>
<p><strong>2:</strong> The error message &quot;TimeoutError: Request timed out&quot; indicates that there's an issue with Kibana's communication with Elasticsearch.</p>
<ul>
<li>Check if the Elasticsearch service is up and running and accessible
from the Kibana pod.</li>
<li>Ensure that the Elasticsearch URL and credentials are correctly configured in the Kibana configuration.</li>
<li>Verify that there are no network policies or firewalls blocking communication between Kibana and Elasticsearch.</li>
<li>Check resource allocation for both Kibana and Elasticsearch pods. Ensure they have enough resources (CPU, memory) allocated to perform
their tasks.</li>
</ul>
<p>I hope this could help you.
Happy Coding</p>
