Skip to content
This repository has been archived by the owner on Mar 4, 2024. It is now read-only.

Detect the default interface #17

Merged
merged 3 commits into from
Aug 11, 2016
Merged

Conversation

mbruzek
Copy link
Contributor

@mbruzek mbruzek commented Aug 11, 2016

With xenial the interface is ens4 the code was expecting eth0 and the assumption breaks the configuration of the flannel interface.

Changed the default behavior to attempt to detect the default interface when the iface configuration option is None or "".

Take that !

edit: closes #16

@lazypower
Copy link
Contributor

lazypower commented Aug 11, 2016

Readme 👮 wants more details about what this does

@lazypower
Copy link
Contributor

🏆 This is a great fix up for #16

I'm over-all really happy with this proposal. One thing I would like to suggest is to put in the status-history which interface it auto-selected so the user has an opportunity to find what interface it picked without remoting into each unit.

juju status-history kubernetes/0 would be good info to have, but its not super critical that go in this merge. Just food for thought for future iterations.

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

Successfully merging this pull request may close these issues.

Behavior of determining network interface is currently cumbersome and does not work by default
2 participants