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

Testing on Azure needed #1

Open
Ulexus opened this issue Apr 20, 2018 · 4 comments
Open

Testing on Azure needed #1

Ulexus opened this issue Apr 20, 2018 · 4 comments

Comments

@Ulexus
Copy link
Member

Ulexus commented Apr 20, 2018

The Azure implementation has been added purely on the documentation. Live testing needs to be done to validate it.

@juansalvatella
Copy link

I've recently done a test in Azure and it's not working properly. I'll have a look and submit a pull request if I find out what's wrong.

@Ulexus
Copy link
Member Author

Ulexus commented Jun 26, 2020

I have used this on Azure before; I recall the results being weird, but I do not recall exactly how.

@juansalvatella
Copy link

Could it be that the Azure Kubernetes Service doesn't provision a public IP to the nodes in the cluster? I'd say that's why netdiscover is not picking up the IP... there is none.

@Ulexus
Copy link
Member Author

Ulexus commented Jun 26, 2020

Yes, that is certainly true of the default node setup. However, you can set them to get a public IP. I seem to recall that even in that case, something was weird.

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

No branches or pull requests

2 participants