Skip to content
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

Add the 'config' block to the 'upstream' section #11412

Closed
sergeyzoom opened this issue Oct 29, 2021 · 3 comments
Closed

Add the 'config' block to the 'upstream' section #11412

sergeyzoom opened this issue Oct 29, 2021 · 3 comments

Comments

@sergeyzoom
Copy link

sergeyzoom commented Oct 29, 2021

Add the 'config' block to the 'upstream' section.

Nomad is unable to take an upstream -> config block right now.

Proxy section.upstream[*].the configuration in the nomad configuration causes the error
"Unsupported block type; Configuration type blocks are not expected here".

Because of this, it is not possible to configure the envoy-proxy more fully in the Mesh system.
(Change the protocol, configure the policy of retrays, etc.)

More details were discussed on the forum
https://discuss.hashicorp.com/t/service-mesh-envoy-upstream-config-blocks-of-type-config-are-not-expected-here/30547

@jrasell
Copy link
Member

jrasell commented Oct 29, 2021

Hi @sergeyzoom and thanks for raising this issue. We already have #11392 which requests this feature, therefore I will close this issue out and use the existing one. If you could add an additional thumbs up on #11392 that would be great and helps prioritise.

@jrasell jrasell closed this as completed Oct 29, 2021
@jrasell jrasell added stage/duplicate theme/consul/connect Consul Connect integration labels Oct 29, 2021
@jrasell
Copy link
Member

jrasell commented Nov 2, 2021

Hi @sergeyzoom. I understand that which is why the linked issue is a Nomad issue to track making this available from the Nomad side. Please let me know if I am missing anything else.

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants