You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.
Instead of a separate weave launch-dns step, we should launch weavedns by default, as part of weave launch. Unless the user specifies a --without-dns option.
This does depend on #22 somewhat, in that weavedns needs an IP (and subnet), and we don't really want to clutter weave launch with that information, at least not by default.
A few other points need consideration:
if we pick the IP and subnet automatically, should it be possible to override that choice?
should it still be possible to launch (and stop) weavedns separately?
We want to avoid option/command clutter, so unless we have compelling use cases for needing the above, we should refrain.
The text was updated successfully, but these errors were encountered:
Instead of a separate
weave launch-dns
step, we should launch weavedns by default, as part ofweave launch
. Unless the user specifies a--without-dns
option.This does depend on #22 somewhat, in that weavedns needs an IP (and subnet), and we don't really want to clutter
weave launch
with that information, at least not by default.A few other points need consideration:
We want to avoid option/command clutter, so unless we have compelling use cases for needing the above, we should refrain.
The text was updated successfully, but these errors were encountered: