You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.)
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.
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.
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.
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
The text was updated successfully, but these errors were encountered: