Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How do you configure EnvoyProxy with a default (catch-all) route for traffic?

See https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/route/route.proto#envoy-api-msg-route-routematch

 

Assuming you want to have one 'catch-all' or default route in your Envoy Proxy, how do you configure Envoy?  The docs are a bit sparse on exactly what you could do here.

1 answer

1 accepted

0 votes
Answer accepted

Let's assume you have two virtual machines on your dev laptop: serviceProxy and proxyTarget.

You can use the following envoy.conf to achieve the goal.

 

# serviceProxy: 192.168.127.10:{10000,9901}
# proxyTarget: 192.168.127.11:80
#
admin:
access_log_path: /tmp/admin_access.log
address:
socket_address: { address: 0.0.0.0, port_value: 9901 }

static_resources:
listeners:
- name: catch_all_proxy_rule
address:
socket_address: { address: 0.0.0.0, port_value: 10000 }
filter_chains:
- filters:
- name: envoy.http_connection_manager
config:
stat_prefix: ingress_proxyTarget
route_config:
name: default_route
virtual_hosts:
- name: default_vhost
domains: ["*"]
routes:
- match: { prefix: "" }
# route: { host_rewrite: proxyTarget.local, cluster: proxyTarget }
route: { cluster: proxyTarget }
http_filters:
- name: envoy.router
clusters:
- name: proxyTarget
connect_timeout: 0.12s
type: LOGICAL_DNS
# Comment out the following line to test on v6 networks
dns_lookup_family: V4_ONLY
lb_policy: ROUND_ROBIN
hosts: [{ socket_address: { address: 192.168.127.11, port_value: 80 }}]

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

307 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you