-
Notifications
You must be signed in to change notification settings - Fork 7
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
Fix envoy dynamic forward proxy config #38
Conversation
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.
LGTM. +1 for merging.
Have you tried these changes out @jackkleeman?
@@ -183,7 +183,8 @@ spec: | |||
value: 127.0.0.1:10001 | |||
# ... | |||
- name: envoy | |||
image: envoyproxy/envoy:distroless-v1.26.1 | |||
# use a bleeding edge image until v1.17 is released |
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.
# use a bleeding edge image until v1.17 is released | |
# use a bleeding edge image until v1.27 is released |
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.
Maybe also add the link to the envoy issue which we are waiting on.
yes, its running in the kube cluster already |
Shall we merge this @jackkleeman? |
The current config is not correctly load balancing over different endpoints. We rely on the feature merged in envoyproxy/envoy#26420; this should be in envoy 1.27, in the meantime we can use dev envoy.
0346c7c
to
9dd4695
Compare
✅ Deploy Preview for docsrestatedev ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
The current config is not correctly load balancing over different endpoints. We rely on the feature merged in envoyproxy/envoy#26420; this should be in envoy 1.27, in the meantime we can use dev envoy.