envoy

Gloo Edge Version

1.10.x (latest stable)

Kubernetes Version

1.21.x

Describe the bug

When a request is rate-limited, we should see the RL flag in the Envoy access logs.

In version 1.10, the flag is left empty -

Steps to reproduce the bug

GIST: https://gist.github.com/bcollard/9cfaa5a36247ea42dd14b6c2b48eeb56

Expected Behavior

response flag with

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

What happened?

As parsing time.Duration works only with time periods (i.e 1m, 24h, 23h59m etc.) you cannot specify period in days/months/years as we suggests in help/docs of our commands:
https://github.com/kumahq/kuma/blob/8708885a8ef244f0806aa7d5dae08c7dde64a7bb/app/kumactl/cmd/generate/generate_zoneingress_token.go#L29
we can fix it by changing flag description/help, but I think we

Current State

Clicking the contributing breadcrumb (See top of first image) leads to a 404

On link in

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

@Abhijay007 has been a consistent contributor and community member.

Desired Situation
Let's recognize @Abhijay007 as a contributor and community member by creating a profile on https://layer5.io/community/members.

• GitHub: Abhijay007
• Twitter: CodeInVeins
• LinkedIn: /abhijay-jain-551b01193
• Link to profile picture:

A detailed explanation on how to set u