cloud-native

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

At the moment, the Redis clients does not support all the commands supported by recent versions of Redis: see quarkusio/quarkus#18351 for example.
However the backing vertx-redis-client provides a way to craft commands using .send(Request.Command) method.
See quarkusio/quarkus#18351 (comment) for example. We c

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

PodSecurityPolicy is deprecated as of k8s v1.21 and will be unavailable starting k8s v1.25. We're seeing such warnings when installing linkerd under newer k8s versions:

Warning: policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
podsecuritypolicy.policy/linkerd-linkerd-control-plane created

We have one PSP: linkerd-linkerd-control-plane and its co

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

The default_conn_delay of the limit-conn plug-in is used to control the delay of forwarding to upstreams when the connection exceeds a certain threshold, but after actual testing, it is found that this delay time is not strictly in accordance with the configured delay time.

https://github.com/openresty/lua-resty-limit-traffic/blob/master/lib/resty/limit/conn.lua#L98-L101

currently, yb-ts-cli does not return any success message on the the completion of compaction.

 ./yb-ts-cli --server_address=<ip>:9100 compact_all_tablets

It would be nice addition if a user friendly message is added.

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"
},

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

Question

As we updated the spec of CRD, the script test always fail, because it use the updated CRD in the PR and outdated image on the dog docker hub.

We need rebuild these images each time.

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?