Can anyone please help me out. I'm getting error while generating KONG client credentials on HTTP port 8000.

{ "error_description": "You must use HTTPS", "error": "access_denied" }

I have added trusted_ips = 0.0.0.0/0,::/0 in kong.conf also, but it didn't work.

我们鼓励使用英文，如果不能直接使用，可以使用翻译软件，您仍旧可以保留中文原文。
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

Any hover effects doesn't properly applied to all header elements (top line with cluster name and cluster menu). It seems that something placed on top of them and covers most of their height.

https://user-images.githubusercontent.com/9607060/108056014-cd186a00-7061-11eb-8ac0-5d01e206e636.mp4

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.

This is based on #6160: if an opaque-ports is set on a workload (e.g a pod template in a Deployment) but not on its corresponding service, then the opaque_transport is correctly set on the endpoint however we still do protocol detection. This results in an unexpected Opaque Transport header picked up by the inbound proxy (concluding with a closed conn):

[    19.551490s] DEBUG ThreadId

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

We already have a yb-ts-cli compact_tablet, but that works strictly on the TS side. We should be able to add a similar RPC on the master side, reusing the same logic of triggering the respective tablet/rocksdbs to flush.

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

nacos doc https://nacos.io/en-us/docs/open-api.html#2.4

Default namespaceId is public,It should be configurable

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

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.

Bug Report

https://github.com/chaos-mesh/chaos-mesh/blob/master/controllers/awschaos/ec2stop/types.go#L56-L60 These lines of codes make it possible to use another endpoint (like localstack) to do AWS experiments. However, the Recover of ec2stop and other kinds of chaos doesn't have these codes.

It was amazing that even with this bug, the integration test has passed. The expected pheno

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

What problem are you facing?