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

Wiki 文档

配置的优先级
文档中写到“优先级关系是:A < B < C”，存在歧义容易造成混淆，建议修改。
应使用更为确切的说法，优先级的定语是“高和低”而不是“大和小”，并不一定所有读者都有“优先级数值小即优先级高”的认知
同时，例子中使用 A、B 和 C 亦没有体现出数值的概念，进一步加深了读者的疑惑。
如：“优先级大”、“优先级数值小”和“优先级高”，是否应选择“优先级高”才是最清晰的表达方式？

What would you like to be added:

Lens should keep object details panel open even when related object has been removed from k8s api.

Why is this needed:

It would make debugging of these pods show much easier. It's pretty annoying to see details panel closing just when you are trying to read/copy some critical information from there.

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
Now that https://github.com/quarkusio/quarkus/blob/master/independent-projects/tools/devtools-common/src/main/java/io/quarkus/devtools/commands/CreateExtension.java is common, we can easily add a new command to the Quarkus CLI to create extension.

Following quarkusio/quarkus#13896

Latest chart fails to install CRD

Description

I installed openebs using following commands:

kubectl create ns openebs
kubectl config set-context $(kubectl config current-context) --namespace openebs
helm install openebs stable/openebs --version 1.10.0 --set crd.enableInstall=false --set rbac.pspEnabled=true

And here are two pods in CrashLoopBackOff:

$ ku

If the main Linkerd control plane has been uninstalled, it is no longer possible to uninstall the multicluster extension.

Uninstalling the multicluster extension should not required the main control plane.

bin/linkerd mc uninstall | k delete -f -
Error: you need Linkerd to be installed in order to install multicluster addons
Usage:
  linkerd multicluster uninstall [flags]

Feature Description

Kubersphere integrate the velero based on the k8s CRD extensions

How does it work
It's like monitoring component

See https://docs.yugabyte.com/latest/admin/yb-admin/#modify-placement-info for the current usage of modify-placement-info. Currently this precludes users from specifying how many replicas belong in each availability zone specified. To fix, this make the placement_info field a comma separated list of cloud1.datacenter1.rack1:num_replicas.

Currently the system.authz policy can only return a boolean decision indicating whether the API request to OPA should be allowed. Often, administrators want to be able to provide a reason why the API request is denied. We should extend the built-in authorizer to support a structured response from the policy

Improve Docs

Please describe which part of docs should be improved or typo fixed

1、In the How to set the TCP server address example, curl http://127.0.0.1:9080//apisix/admin/plugin_metadata/error-log-logger After the port number is //, we should change It is modified to /.

[https://github.com/apache/apisix/blob/master/doc/plugins/error-log-logger.md#how-to-set-the-tcp-server-

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

chaos-daemon doesn't have any authentication mechanism, which means any client in the cluster could modify the iptables and ipset config / cause stress / inject IO latency for nearly all the pods.

gRPC with server side SSL/TLS authentication is enough. However, it may break the chaosctl (which is definitely an evidence for the risk), or we need to distribute the certificate to it (or it can

Task

Convert CI to GitHub Actions

Context

Travis is removing its free tier for OSS projects, so this should be built with GitHub Actions instead, which is not going to add additional cost.

I would expect this to be one of the easier projects to convert given that Docker isn't used in the build.

See also:

https://github.com/mvdan/github-actions-golang
https://github.com/ac