Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting UnkownHostException from SpringBoot Microservice running on top of kubernetes #637

Open
maulikprajapati opened this issue Jun 19, 2024 · 3 comments
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@maulikprajapati
Copy link

maulikprajapati commented Jun 19, 2024

What happened:
My application is running on top of kubernetes 1.26.
I am getting sometime (not frequent) an exception from Some microservices (spring-boot 2.7.RELEASE using base image
eclipse-temurin:17-jre) trying to request another service through k8s servicie name. telling me UnknownHostException..
That means the service which initiating the request is not able to resolve hostname.

What you expected to happen:
I am expecting to not see this exception and all calls are DNS resolvable.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

I Tried to make a script which run nslookup command 10000 time and i did not get any error and all calls to service were
resolved successfully.
This issue happen from today only where there is no change related dns .

@kundan2707
Copy link
Contributor

/kind support

@k8s-ci-robot k8s-ci-robot added the kind/support Categorizes issue or PR as a support question. label Jul 2, 2024
@hinst
Copy link

hinst commented Aug 2, 2024

I have been observing UnknownHostException in Docker using eclipse-temurin:17-jdk. I believe the error is caused by the Docker image.

If you look at the version history of the Docker image https://hub.docker.com/layers/library/eclipse-temurin/17-jdk/images/sha256-3f4fd8f15f322224c64e6028a2fe6ae2c648904ff9b5b8fd30f785974adab9da?context=explore you will notice that the image gets updated frequently. Right now it shows LAST PUSHED 8 days ago. I believe a buggy version of the image got pushed at some point

The error is probably not related to Kubernetes directly, because for me it happens even when running in Docker without Kubernetes

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

5 participants