Skip to content

Conversation

ehsjoar
Copy link
Contributor

@ehsjoar ehsjoar commented Sep 8, 2025

Added documentation for MetalLB in BGP mode.

Copy link
Contributor

@alknopfler alknopfler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In general, I'm wondering why we're doing this guide in k3s and not rke2(it's not only your PR...it was there before). But related to your PR, LGTM

@alknopfler alknopfler self-requested a review September 8, 2025 15:00
alknopfler
alknopfler previously approved these changes Sep 8, 2025
Copy link
Contributor

@alknopfler alknopfler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM as we talked... let's discuss the points I mentioned internally to be updated in next sprints

Copy link
Collaborator

@ranjinimn ranjinimn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ehsjoar I have completed my first round of review and suggestions. Please let me know if you have any questions. Thanks

@ehsjoar
Copy link
Contributor Author

ehsjoar commented Sep 9, 2025

I hope I addressed all comments

Copy link
Collaborator

@ranjinimn ranjinimn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM :)

@hardys hardys changed the title First draft Add MetalLB BGP documentation Sep 10, 2025
Copy link
Contributor

@hardys hardys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - couple of small comments:

  • I adjusted the title, IMO it's best to use a descriptive title and for draft PRs use "Convert to Draft" (so the PR can't be accidentally merged, and so we have a descriptive title for the commit message if we squash-merge)
  • I agree with Alberto that we may want to revisit the structure in future - for now this is fine, but perhaps we should in future consider moving some/all of this content under the SUSE Telco Cloud section?
  • We need to reach a conclusion re the support status, if it's TP we should indicate this in the new docs (and release notes when we prepare them)

@hardys hardys merged commit f6dc2be into suse-edge:main Sep 10, 2025
1 check passed
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