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

Grab IP from containers sharing network namespace #507

Merged
merged 1 commit into from
Dec 15, 2016

Conversation

balexx
Copy link
Contributor

@balexx balexx commented Dec 15, 2016

Kubernetes pods create a single container which holds the IP for all other containers in the pod. Thus, when using Registrator, services could appear without an IP address. This PR solves that issue by detecting the namespace is shared, and extracting the IP information from the container holding it.

@mattatcha mattatcha merged commit d2c9de8 into gliderlabs:master Dec 15, 2016
arentrue pushed a commit to rbkmoney/registrator that referenced this pull request Jan 25, 2017
@ganeshkaila
Copy link

ganeshkaila commented Mar 23, 2017

@balexx Looks, the PR #507 is not working well for k8s v1.5. Can you please check?

@balexx
Copy link
Contributor Author

balexx commented Mar 23, 2017

@meganesh it's working well for me on k8s 1.5 on bare metal nodes. I didn't test on GKE, as referenced here.

And please don't throw a comment every few minutes, I don't work in Registrator tech support :-)

@ganeshkaila
Copy link

Sorry for that @balexx. I have found some workaround for my issue. Thanks for your help so far.

@gvenka008c
Copy link

@meganesh What is the workaround? can you please provide some info?

@ganeshkaila
Copy link

Hi @balexx, Can I know the docker version on your bare metal (where docker container of kubernetes can show their IP Address)?

@balexx
Copy link
Contributor Author

balexx commented Apr 18, 2017

@meganeshkaila sure, we're currently on 1.12.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants