Repository navigation
Conversation
Contributor
Author
|
@roosterfish @elijahgreenstein a small docs addition, could you take a look when you have a moment? |
elijahgreenstein
requested changes
Oct 22, 2026
elijahgreenstein
left a comment
elijahgreenstein
left a comment
Contributor
There was a problem hiding this comment.
Thanks @wak327 for this contribution. A few thoughts on revisions for additional clarity.
wak327
force-pushed
the
doc-internal-address-clients
branch
from
October 22, 2026 21:57
fcff57b to
3b683de
Compare
wak327
changed the title
Contributor
Author
|
@roosterfish I addressed @elijahgreenstein's review: the note no longer mentions a specific CLI command and now says explicitly that it's about users accessing LXD. Could you take a look? |
elijahgreenstein
requested changes
Oct 23, 2026
…nal traffic address Signed-off-by: Waleed Khalid <wak327@gmail.com>
…raffic address Signed-off-by: Waleed Khalid <wak327@gmail.com>
wak327
force-pushed
the
doc-internal-address-clients
branch
from
October 25, 2026 18:01
3b683de to
287f254
Compare
Contributor
Author
|
@roosterfish @elijahgreenstein I applied the latest suggestions. Could you take another look? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #956
As suggested in #956 (comment), this adds a note that the address selected for MicroCloud's internal traffic is also the one users accessing LXD usually connect through.
LXD listens on all addresses (
core.https_addressis[::]:8443), butcluster.https_addressis set to the selected internal address. That makes it the address LXD advertises for each cluster member, for example inlxc cluster listand in links to the LXD UI.Changes:
doc/reference/requirements.md: a short paragraph under "Network interface for intra-cluster traffic".doc/how-to/initialize.md: a one-line hint at the address selection step, so users pick an address on a network those accessing LXD can reach.Checklist