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.

版本：2.2.6
https://github.com/alibaba/spring-cloud-alibaba/blob/387dd46fa4d037dad3d7091fca2274d4cc1d5034/spring-cloud-alibaba-starters/spring-cloud-starter-alibaba-nacos-discovery/src/main/java/com/alibaba/cloud/nacos/registry/NacosServiceRegistry.java#L40-L60

在NacosServiceRegistry里引用NacosServiceManager是采用直接注入的方式，当在我想在项目中实现注册多个Nacos注册中心时，就没办法复用此类，建议引用NacosServiceManager的方式和引用NacosDiscoveryProper

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.

After PR #1401 merged, many of our sub modules are failing lint, we should fix all of them.

To fix these, take a look at hack/.lintcheck_failures for a list of currently lint failed modules.

You can check a module by removing it from the .lintcheck_failures list and running make fix to auto fix some lint errors.

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.

In a typical image search task, we send image with dimensionality of B, C, H, W into a deep learning model, where:

• B refers to batch_size.
• C refers to channels, e.g. RGB is 3 channel image while grey-scale image only have 1 channel
• H is the image height
• W is the image width.

By default Jina executors and Finetuner use an argument channel_axis which allow user to mo

Summary

As of v3.2.0, an integration with Argo Dataflow has been added to the Workflow UI, but the integration isn't really documented on the project page, and the errors that pop up when trying to access the new pipelines tab don't really give much indication of what is supposed to be providing the pipeline functionality.

Currently, if someone new to Workflow deploys the Workflow stack and

Description

Since #20895 this should be straight forward to implement.

Implementation ideas

Just like any other DB we already support.

Steps/Code to reproduce:

We've seen a searchResultBufFlags array in proxy task scheduler.
It is never cleaned from the map so I guess there is a memory leak especially when search number is going up.

We need to check on how to fix it

Expected result:

Delete or clean it when ne

Bug Report

What is the issue?

Web dashboard "show" (or maybe suggests) deprecate CLI command

How can it be reproduced?

Possible solution

Chang

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

Issue description

Currently I has test the proxy-mirror plugin in apisix, but I find that the feature of this plugin is different from the ngx_http_mirror_module in nginx. The mirror moudle of nginx can add the uri behind the host in "proxy_pass" directive, for example

location / {
mirror /mirror;
proxy_pass http://backend;
}

location = /mirror {
internal;
proxy_pass http://t

What's it about?
Upgrade Ingress API to networking.k8s.io/v1.

What's the reason why we need it?
Ingress is the core component that is used by the KubeSphere Routes feature. KubeSphere is still using the old api "extensions/v1beta1" both Frontend and Backend. However "extensions/v1beta1" Ingress is deprecated in v1.14+, unavailable in v1.22+. So we need to upgrade it to the latest v

Is your feature request related to a problem? Please describe.

Missing functionality to update min/max cpu/mem of an exiting ENV. Currently, to update, we are forced to delete and re-create the env. This also has a risk of dependent functions being erratic. It also de-couple resource utilization independent of function creation and be useful to update the resource in a quick to respond situ

Expected Behavior

At https://github.com/open-policy-agent/opa/blob/main/bundle/bundle_test.go#L31, the result of function Equal not used:

m.rootSet().Equal(stringSet{"x/y": struct{}{}, "y/z": struct{}{}})

while this function has no side effect:

func (ss stringSet) Equal(other stringSet) bool 

There are multiple issues with the individual beta feature flags. I believe the core issue is lack of understanding of parser_ybc_beta_feature. See the definition:

#define parser_ybc_beta_feature(pos, feature, has_own_flag) \
    check_beta_feature(pos, yyscanner, has_own_flag ? "FLAGS_ysql_beta_feature_" feature : NULL, feature)

If has_own_flag is true, there should be a c

How are you planning on using kubeedge?

I've been looking for something like this for a long time (Currently our team uses Rancher although their product wasn't really meant for edge computing.) I'd love to hear how others in the community would like to use this so I can compile a list of use cases that kubeedge can support out of the box.

Thanks!