envoy

Is your feature request related to a problem? Please describe.
Gloo Edge helm charts should be verifiable, using the provenance file mechanism.

Describe the solution you'd like
Charts should be signed and provenance files uploaded to the helm chart repository. Helm [install|pull|fetch] --verify ... should succeed.

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

Description

Make sure that FULL_URL is the current full url (ie: http://helloworld.com/ingress/kuma/gui, so that it works even if we have an Ingress in front of it that does URL rewrite.

Current Behavior

When we hover on top of the chevron in the navigator there's no change in the cursor.

Desired Behavior

The cursor should switch to a pointer on the chevron to indicate that it's clickable.

Environment

• Browser: Safari
• Host OS: Mac
• Meshery Server Version: stable
• Meshery Client Version: stable
• Platform: Kubernetes

Contribu

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
Currently, the Resources area looks exactly like the Blog area

Desired Situation
We're in need of figuring out how we want to change the way visitors navigate this interface so that it isn't just a repeat of the blog collection, but a perusable catalog of topics. It's ok to include repetitive content from /events, /blogs, /news. Filters that we'll want to account for