Skip to content

Add edge mixer template. #6408

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Conversation

jeffmendoza
Copy link
Contributor

The edge template can be used by adapters that wish to construct a
mesh graph based on observed traffic edges.

@jeffmendoza
Copy link
Contributor Author

cc @quentinmit

// apiProtocol: api.protocol | "Unknown"
// contextProtocol: context.protocol | "Unknown"
// ```
message Template {
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we want/need some discussion of edges being between workload instances here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm not sure that the template dictates what the adapter chooses to constructs the graph based on.


// Protocol used
string context_protocol = 30;
string api_protocol = 31;
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we imagine extending this to include any of the following:

  • api.operation
  • destination.service.name ( and/or destination.service.namespace)
  • connection.mtls

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Those sound reasonable to add, and are likely useful to adapters.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I decided to just add destination.service.uid, as that can be used to put service nodes in a graph. The others are simply more data about an edge. They seem useful, but there are many attributes that seem useful, I woudln't know where to draw the line. Any useful edge data can be added to the template in the future without breaking backwards compatibility.

@@ -432,6 +432,24 @@ spec:
version: v1alpha2
---

kind: CustomResourceDefinition
Copy link
Contributor

Choose a reason for hiding this comment

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

@guptasu just to confirm, this is still where we are putting new templates, correct?

@douglas-reid douglas-reid requested a review from guptasu June 20, 2018 22:15
@codecov
Copy link

codecov bot commented Jun 21, 2018

Codecov Report

Merging #6408 into master will decrease coverage by 1%.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master   #6408    +/-   ##
=======================================
- Coverage      71%     71%   -<1%     
=======================================
  Files         353     353            
  Lines       30814   30717    -97     
=======================================
- Hits        21689   21575   -114     
- Misses       8273    8299    +26     
+ Partials      852     843     -9
Impacted Files Coverage Δ
...olarwinds/internal/papertrail/papertrail_logger.go 59% <0%> (-21%) ⬇️
pilot/pkg/config/memory/monitor.go 82% <0%> (-9%) ⬇️
mixer/adapter/circonus/circonus.go 71% <0%> (-3%) ⬇️
mixer/adapter/stackdriver/metric/bufferedClient.go 91% <0%> (-3%) ⬇️
pilot/pkg/serviceregistry/kube/controller.go 65% <0%> (-2%) ⬇️
mixer/adapter/prometheus/prometheus.go 100% <0%> (ø) ⬆️
mixer/adapter/memquota/dedup.go 100% <0%> (ø) ⬆️
pilot/pkg/model/controller.go 100% <0%> (ø) ⬆️
mixer/adapter/cloudwatch/client.go 0% <0%> (ø) ⬆️
mixer/adapter/servicecontrol/client.go 0% <0%> (ø) ⬆️
... and 6 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cd50f12...2b6b86f. Read the comment docs.

Copy link
Contributor

@douglas-reid douglas-reid left a comment

Choose a reason for hiding this comment

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

/lgtm

@istio-testing
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: douglas-reid, jeffmendoza

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

The pull request process is described here

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

@istio-testing
Copy link
Collaborator

New changes are detected. LGTM label has been removed.

@jeffmendoza
Copy link
Contributor Author

Merge conflicts fixed

The edge template can be used by adapters that wish to construct a
mesh graph based on observed traffic edges.
@istio-testing
Copy link
Collaborator

istio-testing commented Jun 28, 2018

@jeffmendoza: The following tests failed, say /retest to rerun them all:

Test name Commit Details Rerun command
prow/istio-pilot-e2e.sh 6d7ab9a7cc541b08e06dcdcccf2fd51d4789594d link /test istio-pilot-e2e
prow/e2e-bookInfoTests.sh 6d7ab9a7cc541b08e06dcdcccf2fd51d4789594d link /test e2e-bookInfo

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

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