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

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

Description
We have to continuously push for quality, thus we always need to improve our testing and test coverage. Any improvement of testing is a great contribution to jina.

If you have no idea how to get started on this, here there are some ideas that could be good to have.

• Increase coverage
  Checking the reports on `https://codecov.io/gh/jina-ai/jin

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

Community Slack user had a question regarding how to find the exact size of any table ycqlsh shell or tserver-UI.

Context - https://yugabyte-db.slack.com/archives/CG0KQF0GG/p1623851330364200

Here is where we stand today:

• No support for this through ycqlsh
• 2 types of support through the UI: (1) Per tablet server, which you can see on the tables tab of the tserver UI, but you’d have

Issue description: Apisix stream_routes's parameter "remote_addr" only support single ip, needs to support multiple ip or match rules like "192.168.0.0/16", just like http routes parameter "remote_addr"

Environment

Request help without environment information will be ignored or closed.

• apisix version (cmd: apisix version): 2.6
• OS (cmd: uname -a): CentOS7
• OpenResty / Ng

Expected Behavior

According to the documentation https://www.openpolicyagent.org/docs/v0.29.4/rest-api/#health-api GET /health?bundles HTTP/1.1 can be used to determine if bundle activation is ok or not.

Two codes are possible:

• 200 when it is ok
• 500 when it is not ok

Let's consider following configuration :

• a OPA server using bundle through the configuration file
• bundle

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

refs to https://pkg.go.dev/sigs.k8s.io/controller-runtime/pkg/envtest#pkg-constants, the actual usful env is USE_EXISTING_CLUSTER not TEST_USE_EXISTING_CLUSTER, and we have used the former for a while. 😰

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?