-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Remove cluster.hosts #4959
Remove cluster.hosts #4959
Changes from all commits
db13dc0
08f1700
a534afc
3a030ad
4674de3
215c0ae
3e9e1fa
b49ac98
f12c103
055d6d4
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -97,29 +97,44 @@ static_resources: | |
type: STRICT_DNS | ||
connect_timeout: 0.25s | ||
lb_policy: ROUND_ROBIN | ||
hosts: | ||
- socket_address: | ||
protocol: TCP | ||
address: disccovery.yourcompany.net | ||
port_value: 80 | ||
load_assignment: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Have you validated all of these modified YAML? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I randomly tested them manually. Will have another test session today. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hum, I think @srikailash or @junr03 probably could give some tips on testing these templates here. 🙂 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @dio reached out over slack. For the v2 templates I suggest doing what I asked @srikailash to do when we converted them from v1 to v2: render the templates into config files and run them over the validation server, and the config_test |
||
cluster_name: sds | ||
endpoints: | ||
- lb_endpoints: | ||
- endpoint: | ||
address: | ||
socket_address: | ||
protocol: TCP | ||
address: discovery.yourcompany.net | ||
port_value: 80 | ||
- name: statsd | ||
type: STATIC | ||
connect_timeout: 0.25s | ||
lb_policy: ROUND_ROBIN | ||
hosts: | ||
- socket_address: | ||
protocol: TCP | ||
address: 127.0.0.1 | ||
port_value: 8125 | ||
load_assignment: | ||
cluster_name: statsd | ||
endpoints: | ||
- lb_endpoints: | ||
- endpoint: | ||
address: | ||
socket_address: | ||
protocol: TCP | ||
address: 127.0.0.1 | ||
port_value: 8125 | ||
- name: lightstep_saas | ||
type: LOGICAL_DNS | ||
connect_timeout: 1s | ||
lb_policy: ROUND_ROBIN | ||
hosts: | ||
- socket_address: | ||
protocol: TCP | ||
address: collector-grpc.lightstep.com | ||
port_value: 443 | ||
load_assignment: | ||
cluster_name: lightstep_saas | ||
endpoints: | ||
- lb_endpoints: | ||
- endpoint: | ||
address: | ||
socket_address: | ||
protocol: TCP | ||
address: collector-grpc.lightstep.com | ||
port_value: 443 | ||
http2_protocol_options: {} | ||
{% for service, options in clusters.iteritems() -%} | ||
- {{ helper.internal_cluster_definition(service, options)|indent(2) }} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
??? Can you set DNS addresses in load assignment ?
And how long has this been implemented? i.e. was it available in Envoy as of June 2018? The reason I am asking is because we can update this in Istio as well as long as we can support Envoys from around istio 1.0 (which is around june)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For istio-1.0 releases, we already switched to forked Envoy with necessary patches
https://github.com/istio/proxy/blob/release-1.0/WORKSPACE#L38
So I don't think this will affect that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think yes. It is implemented since this: #3864
The relevant discussion probably here: #3261 (comment)