envoy

Gloo Edge Version

1.12.x (beta)

Kubernetes Version

No response

Describe the bug

Need to move VALIDATION_MUST_START definition from gateway deployment to gloo deployment now that gateway pod is removed
https://github.com/solo-io/gloo/blob/master/install/helm/gloo/templates/5-gateway-deployment.yaml#L92

If there are any values that might be set with gateway.deployment.custom

The "Introduction to Contour" link on the projectcontour.io landing page points to a blog from 2019 that references Contour v0.10, this link should be updated to point to something newer, or perhaps we could drop that entire section as it seems somewhat redundant with other ways to navigate the site.

Description

There are use-cases where mesh admins might want to limit the total numbers of DPPs in a mesh. This can be used to avoid an accidental deployment to bring the cluster to a halt.

Current State

The current table of contents does not have Cilium Service Mesh listed.

Desired State

Add an entry for Cilium Service Mesh pointing to /service-meshes/adapters/cilium

(https://docs.meshery.io/s

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 am doing unit tests for my filter with DispatchHttp, something like this:

_, err = proxywasm.DispatchHttpCall(ctx.clusterName, headers, body, nil, ctx.timeout, ctx.callback)
	if err != nil {
		proxywasm.LogCriticalf("big error: %v", err)
		proxywasm.ResumeHttpRequest()
		return types.ActionContinue
	}

I don't know of a way to mock the DispatchHttpCall method in order to re

Current Behavior
The repo at github.com/meshery/meshery-perf is new and is not yet listed in the Community Handbook's repository overview.

Desired Behavior
Create an entry for the new meshery/meshery-perf repo in the repository overview.

<img src="https://raw.githubusercontent.com/layer5io/layer5/master/.github/as

This is more a discussion than an issue. Would it be valuable to move every example into it's own folder and include a matching envoy config + docker compose config? This should allow developers exploring the proxy-wasm SDK to run the example easily.

If this is considered valuable, I can contribute the changes.