Skip to content

Updating description of network definitions#664

Merged
rshriram merged 3 commits intoistio:masterfrom
rshriram:update_comments
Oct 21, 2018
Merged

Updating description of network definitions#664
rshriram merged 3 commits intoistio:masterfrom
rshriram:update_comments

Conversation

@rshriram
Copy link
Copy Markdown
Member

Signed-off-by: Shriram Rajagopalan shriramr@vmware.com

Shriram Rajagopalan added 2 commits October 19, 2018 19:54
Signed-off-by: Shriram Rajagopalan <shriramr@vmware.com>
@istio-testing
Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: rshriram

If they are not already assigned, you can assign the PR to them by writing /assign @rshriram in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@googlebot googlebot added the cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. label Oct 19, 2018
repeated string registries = 2;
message NetworkEndpoints {
oneof ne {
// A CIDR range for the set of endpoints in this network
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Few more words here ? It assumes the endpoints in the mesh have non-overlapping CIDR ranges ?

An endpoint will be assigned to a network:

  1. directly by the registry, if it can infer the network from its backends
  2. by matching the registry name with one of the "from_registries" in the mesh config. A "from_registry" can only be assinged to a single network.
  3. by matching the IP against one of the CIDR ranges in a mesh config network. The CIDR ranges must not overlap and be assigned to a single network.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

by matching the registry name with one of the "from_registries" in the mesh config. A "from_registry" can only be assinged to a single network.

@costinm What do you mean by from_registries? I can not find it.

Signed-off-by: Shriram Rajagopalan <shriramr@vmware.com>
@rshriram rshriram merged commit b3f5d5d into istio:master Oct 21, 2018
rshriram added a commit to rshriram/api that referenced this pull request Oct 21, 2018
* clarity

Signed-off-by: Shriram Rajagopalan <shriramr@vmware.com>

* renaming

* nits

Signed-off-by: Shriram Rajagopalan <shriramr@vmware.com>
ymesika pushed a commit to ymesika/api that referenced this pull request Oct 21, 2018
* clarity

Signed-off-by: Shriram Rajagopalan <shriramr@vmware.com>

* renaming

* nits

Signed-off-by: Shriram Rajagopalan <shriramr@vmware.com>
rshriram pushed a commit that referenced this pull request Oct 21, 2018
* Updating description of network definitions (#664)

* clarity

Signed-off-by: Shriram Rajagopalan <shriramr@vmware.com>

* renaming

* nits

Signed-off-by: Shriram Rajagopalan <shriramr@vmware.com>

* Added MeshNetworks
// The names of the registries should correspond to the secret name
// that was used to configure the registry (kubernetes multicluster) or
// supplied by MCP server.
string from_registry = 2;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

can you explain how this can be used? I am still confused after through the istio code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants