After Update 22.1 Jarvis Pod Failed to resolve hostname
Article ID: 257605
Updated On:
Products
Issue/Introduction
After upgrading DX APM to version 22.1, Pod Jarvis is experiencing error
Failed to resolve hostname.
As a workaround, it is necessary to scale down jarvis-elasticsearch, restart the Kubelet and Docker services on the Elasticsearch node and then start the scale up jarvis-elasticsearch. We would like have permanent solution of this issue.
Environment
Release : 22.1
Resolution
This is not an issue with DX Platform.
It is an issue with k8s cluster and due this issue with k8s cluster, the DX Platform Jarvis Pods encountering this issue.
This issue is specific to k8s, we usually observe this issue whenever server/node gets restarted, please check with the k8s cluster admin.
Please also check this article which can help here, however please try it in NON PROD first and confirm it that it is working, before doing it in PROD.
Also, during the error you can check with k8s admin to see any network issue for the nodes/k8s cluster.
Feedback
