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

What would you like to be added:
Now it's only possible to see if pod / deployent / daemonset / statefulset is using hostNetwork by opening the object in edit mode. Would be nice if Lens showed that on object details directly.

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

Ability to reuse a shared server launched by dev services across multiple Quarkus apps

Implementation ideas

This should be label based discovery just like what we have for Kafka and AMQP

We have separate CI and CD pipelines, which share a lot of code actually (like the testing part). This is a bit annoying to maintain at the moment, because we have to do all changes twice. It would be great do modularize this somehow so that both workflows

The proxy-metrics diagnostics include potentially private information (service names, pod names, etc).

It would be helpful if this command could support an --obfuscate flag that mangles metric label values like

• authority
• dst_service
• dst_namespace
• target_addr
• server_id
• client_id

Each of these values should be hashed so that values can be correlated but shou

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

Improve Docs

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

Hello, I found that apisix support using "/apisix/admin/plugins/reload" API to reload plugins.
But we don't add description into admin-api.md

Referer: https://github.com/apache/apisix/blob/07bfe5b9c03ad361cb71541eb02fd661f1323213/apisix/admin/init.lua#L28

Describe the solution you'd like

Add "/

Flush/Compact requests to the tServer are rpcs that are expected to take a long time. It does not make sense for these to use the same deadline (20s) and num_retries as other async_rpc_tasks.

We should have these tasks override these settings; similar to what BackfillChunk does to give itself more time; and also to disble/reduce retries in the case of flush/compact.

Without having this, we

Expected Behavior

As I currently understand it is not possible to make OPA decision based on body contents that has content type application/x-www-form-urlencoded.

Actual Behavior

Decision log says "content-type: application/x-www-form-urlencoded parsing not supported".
Also the parsed_body is empty:
`[
{
"type": "string",
"value": "parsed_body"
},

Describe the bug
I have a setup where I use discovery to contact the spring config server. In my case I have both eureka and consul in the pom.xml
If I disable eureka in the bootstrap properties, I expect consul to be picked. It does not, it was working using spring boot 2.1.

Tested with spring boot 2.3.10 and spring cloud Hoxton.SR11

Sample
pom.xml

<dependency>
	<groupId>o

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

😰 I must be drunk when I wrote these code:

// Node defines a single step of a workflow.
type Node struct {
	Name     string        `json:"name"`
	Type     NodeType      `json:"type"`
	State    NodeState     `json:"state"`
	Serial   *NodeSerial   `json:"serial,omitempty"`
	Parallel *NodeParallel `json:"parallel,omitempty"`
	Template string        `json:"template"`
	UID

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?