Next line returns 200 as status https://github.com/Kong/kong/blob/c817fada7a514d84f6e0aab7461605c71bf3a841/kong/plugins/cors/handler.lua#L13

Internet says it should return 204:

• https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request
• https://docs.microsoft.com/en-us/aspnet/core/security/cors?view=aspnetcore-3.1#preflight-requests

Internet changed its mind since 2018 https://

Please answer these questions before submitting your issue.

• Why do you submit this issue?
• Question or discussion
• Bug
• Requirement
• Feature or performance improvement

Question

• What do you want to know?
  Sample rate configuration failure

Bug

• Which version of SkyWalking, OS, and JRE?
  v8.3.0
• Which company or project?
  XiaoMai
• What happ

Issue Description

feature request

Describe what happened (or what feature you want

The bin/test-cleanup script does not delete linkerd extensions which have been installed on the cluster. This can cause subsequent test runs to fail when those extensions are installed again.

The script should be updated to full delete all linkerd extensions. It can use the linkerd.io/extension label to locate all resources associated with an extension. This label may need to be added to

Kiali uses tooltip in multiple locations, in some cases style difers even for the same concepts.

I noticed some changes on this kiali/kiali-ui#1884 but it would require some global issue to review all tooltips and check that they look like similar (at least for the same concept).

Summary

kumactl install control-plane does not respect user overrides of kuma env variables passed with the --env-var flag. This makes it difficult to customize an install past what is officially supported.

Steps To Reproduce

1. kumactl install control-plane --env-var KUMA_DEFAULTS_SKIP_MESH_CREATION=true
2. See the duplicate entries for KUMA_DEFAULTS_SKIP_MESH_CREATION i

openservicemesh/osm#1931 requests to lower the key bit size by default; we would like to have a mechanism to configure the key bit size on OSM, as opposed to a hardcoded value.

Scope (please mark with X where applicable)

• New Functionality [X]
• Envoy Control Plane [X]
• Certificate Management [X]

Possible use cases
Current default-o

We should improve our cluster name validation at cluster registration time. Currently, providing a non-k8s-compliant name will result in the installation of all agent charts but will fail when provisioning the remote service account.

❯ meshctl cluster register --cluster-name cluster1ASD--
INFO[0005] finished installing chart as release: agent-crds
INFO[0008] finished installing char

Create an example walkthrough that focuses on TCP based routing with TLS support.

Current Behavior
The individual service mesh management pages have a namespace field with "default" prepopulated.

Desired Behavior
The namespace field should not only show "default" as an option, but should also include the list of namespaces that are currently present in the user's Kubernetes environment. Pre-populating this text field will be a UX improvement and it will also help