Docs for interconnect feature #3526
Closed
Conversation
This file contains 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
Signed-off-by: Surya Seetharaman <suryaseetharaman.9@gmail.com>
| * ovnkube-master pod | ||
| * ovnkube-cluster-manager container: This is responsible for allocating the hostsubnets per node and giving out the join subnet IP and transit switch port IPs to each node in the cluster. | ||
| * ovnkube-zone pod | ||
| * ovnkube-network-controller container: That talks to kube API service and converts the k8s objects into NBDB logical elements and inserts them into the north bound database using libovsdb client. |
There was a problem hiding this comment.
Suggested change
| * ovnkube-network-controller container: That talks to kube API service and converts the k8s objects into NBDB logical elements and inserts them into the north bound database using libovsdb client. | |
| * ovnkube-network-controller container: That talks to kube API service and converts the k8s objects into NBDB logical elements and inserts them into the north bound database using libovsdb client. It is also responsible for configuring remote chassis' within the SB DB. |
This was referenced May 26, 2023
|
@oribon : I will make sure to do the doc changes for egressQoS in this one as well. |
|
closing in favour of #4213 |
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.
- What this PR does and why is it needed
This PR intends to document the changes related to adding the interconnect feature. The architecture docs are done based on the previous set of presentations done by @trozet and @numansiddique.
In addition to the initial set of docs describing the feature, I will try to document the important changes that happen in case node, pod, service, policies adds and deletions which hope to serve as developer docs that will be based on #3169 and #3366.
This PR will also have developer doc contributions for the egressIP changes from @tssurya, egressSVC changes from @kyrtapz and secondary networks support changes from @jcaamano. The goal is every developer merging stuff should also add developer docs for their respective parts. Also the metrics docs need to be updated accordingly cc @martinkennelly or anyone who does this part of the work.
NOTE: The initial set of developer docs are bound to change over time and reviewers have to be more strict to keep the docs updated and not merge PRs unless that is done in case logic is being changed.
- Special notes for reviewers
FYI: Please try not to nit-pick, I am not a docs writer, but I am happy to change upon reasonable review requests. Goal is to cover IC bits, so requests for non-IC descriptions will be ignored.
- Description for the changelog
Add docs for interconnect