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.

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

Describe the feature
Implement client methods for the following endpoints:

• DELETE /workspaces
• DELETE /flows
• DELETE /pods
• DELETE /peas

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

Issue description

Environment

Bug report without environment information will be ignored or closed.

• apisix version (cmd: apisix version): 2.7
• OS (cmd: uname -a): Darwin Kernel Version 20.3.0
• OpenResty / Nginx version (cmd: nginx -V or openresty -V): openresty/1.19.3.1
• etcd version, if have (cmd: run curl http://127.0.0.1:9090/v1/server_info to get the info fro

When pausing a universe, user has to click the Yes button instead of the expected enter key to submit this form.

This leads to universes left running.

version 2.7.1

Expected Behavior

Test pass

Actual Behavior

Test fail

Steps to Reproduce the Problem

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!

Feature Request

This issue will not introduce any NEW features or any changes to the current architecture. It's only about improving the style of codes, and let it be easier to understand Chaos Mesh's codes.

As Effective Go/Interface checks introduced, we do not need to declare explicitly that one struct implements an interface. So

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?