envoy

Describe the bug
We have some references to the gloo-system left in the Helm chart:

Could be a source of bugs.

Expected behavior
Use {{ .Release.Namespace }}

Additional context

• Gloo Edge version Gloo EE 1.8.11

See release notes for Envoy 1.20.0: https://www.envoyproxy.io/docs/envoy/v1.20.0/version_history/current

http: the HeaderMatcher fields exact_match, safe_regex_match, prefix_match, suffix_match and contains_match are deprecated by string_match.

The wrinkle here is that string_match was added in Envoy 1.20.0 and does not exist in 1.19.x so we cannot use this field as soon as we

Summary

We currently don't good import rules for this. It would simplify readability if these were standardised.

See mesheryctl Command Tracker for current status of commands.

Current Behavior

mesheryctl system token create is used to create a new token in the meshconfig(.meshery/config.yaml) file.

When the token n

Use heptio/workgroup to improve handling of the multiple goroutines that are spawned in each of the discoverers. This will also help us to bubble up errors to main, and handle them appropriately.

An example of this is #224. We wanted to handle the case where re-auth failed 3 times, but there was no good way of bubbling up the error to main.go. We could make reconciler.Run return an error to bub

I'd like to see proxy_get_buffer_status(), e.g. https://github.com/proxy-wasm/proxy-wasm-cpp-host/blob/92f02c0001592199d99f946cea34637ff095a8ba/include/proxy-wasm/wasm_api_impl.h#L147

Also proxy_get_header_map_size() , e.g. https://github.com/proxy-wasm/proxy-wasm-cpp-host/blob/92f02c0001592199d99f946cea34637ff095a8ba/include/proxy-wasm/wasm_api_impl.h#L192

I use these when debugging new ext

Current Behavior
The current handbook doesn't have an FAQ section, the questions are here, some of which are not answered yet.

Desired Situation
Create a separate page for FAQ and add the questions from the above document here (https://layer5.io/community/handbook)

[Optional] Alternatives
<