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://

我们鼓励使用英文，如果不能直接使用，可以使用翻译软件，您仍旧可以保留中文原文。
We recommend using English. If you are non-native English speaker, you can use the translation software.

Which Component
eg. Nacos Discovery, Sentinel

Is your feature request related to a problem? Please describe.
Feign限流降级好像只支持url粒度，能否支持服务粒度，就像对RestTemplate支持两种粒度一样(Feign's current limiting degradation seems to only support URL granularit

What would you like to be added:
I'd like the node view to show ALL allocatable resource on the node, not just the basic CPU/mem/pod amounts.

Why is this needed:
In many cases kubelet reports devices, hugepages etc. as usable resources and having to dive into node yaml via edit button is, eh, bad experience. :)

![Screenshot 2021-05-12 at 16 23 40](https://user-images.githubuser

ActorAdapter will ignore null message with "Adapter function returned null which is not valid as an .."

However, this seems not be documented. For instance, scaladoc/javadoc of pipeToSelf could mention it as well as any other place where adapters are used.

Description

Apparently FSWatchUtil starts an Executor, but the threads this is spawning have name patterns like pool-406-thread-1.

It would be highly preferreable for all of our components to specify a good name for threads which are being started, to help with diagnostics.

Bug Report

What is the issue?

I've successfully got kubernetes CronJobs to work with linkerd-proxy injection by using the linkerd-away wrapper, however if I check the proxy status in the target namespace linkerd check --proxy -n <namespace> the linkerd CLI will never exit. It appears to be stuck checking the proxy container in the "Completed" Pod that is no longer running.

Using `

Local PV (device) provisioner leaves a stale BDC in the following case:

• On PVC request, creates a BDC
• If the system doesn't have a matching BD, then PVC request keeps retrying, and so does the NDM operator that keeps retrying
• Now if the user deletes the PVC, then Local PV (device) provisioner doesn't get the trigger to process delete, as there was no PVC.

This causes the stale BDC

I have been asked several times whether the value filled in cc.spec.common.es.externalElasticsearchUrl requires an http prefix, but it is actually not needed, but this key is a bit confusing. I don’t know if I need an http prefix sometimes when I look at it, so I think it’s clearer to change it to externalElasticsearchUrl to externalElasticsearchHost

/kind feature-request

Would be nice to have an explicit gauge of how long a server has been up. This would be useful in case of server restarts.

Easiest would be to use our new Lag metric facility, eg: MillisLag and maybe even set it up at server registration, eg: RpcAndWebServerBase::GenerateInstanceID

Would love to see support for the strings.Repeat(s string, count int) string go function within OPA's built-in functions.

I am using the output of the walk function to create "fingerprints" of highly nested objects and need to output a list of strings for all paths. I have a work arounds, but this would be much cleaner if the Repeat function were added to builtins.

Expected Behavior

Issue description

Need to config custom timeout for route when route belongs to service or upstream.
Sometimes we don't want to use timeout configured in service or upstream but use custom timeout instead.

Environment

apisix version (cmd: apisix version): 2.3

What would you like to be added/modified:

To improve project stability, we need more tests to cover corner cases.
And the code coverage is around 50% currently, we need to add more tests to improve it.

To improve case coverage, we may need a list of cases to track the work.
For code coverage, simply check bef

currently, we have more than one go.mod file, and we should also cleanup these file during make check.

This feature enables the ipsec backend for Flannel in the k3sup install command

Expected Behaviour

An additional flag to k3sup install should enable ipsec for Flannel as

We have a Jupyter notebook on the README, a good idea could be to expand this to the parts that we have yet a notebook to have a more interactive README.

What problem are you facing?