virtual host options

What steps did you take and what happened:

in the https://projectcontour.io/getting-started/ it gives instructions for using the Operator

kubectl apply -f https://projectcontour.io/quickstart/operator.yaml

and

kubectl apply -f https://projectcontour.io/quickstart/contour-custom-resource.yaml

and specifies:

Deploying Contour using either option crea

Summary

Today our testing infrastructure relies heavily on KinD which is a convenient way to run ephemeral K8s clusters locally. However, since it packs a full K8s distro, it tends to be slow especially when several clusters are run in parallel (e.g. our multi-zone). We surely know docker can do better as spinning a couple of Kuma universal cluster

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

Current State:
The Helm chart for Meshery is available on Artifact Hub - https://artifacthub.io/packages/helm/meshery/meshery

Desired State:
The Kubernetes page should have a section describing the chart and pointing to Artifact Hub -

Contributor Resources

• [Meshery documentation site](https://docs.

Current Behavior

1. The new source and deployment target locations need updating in the contributor guide. See https://github.com/layer5io/layer5/blob/9e24d81e0e4883ab3413bc3cf79f2e639c198349/.github/workflows/gatsby.yml#L18-L19 for details.

2. The Chore/Task Issue template needs updated to remove layer5-ng reference.

Desired Situation

• No references to layer5-ng should rema

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

This is an optimization to reduce the time it takes to build/deploy YAStack.

Compilation of YAStack can be optimized by pre-compiling source code that does not depend on DPDK. This can help build the image faster since now only DPDK and dependent code will have to be compiled.

Ref the Issue

List of filters