Kubernetes

There is a strong and growing consensus in sig-node about the need of increasing the test coverage in the kubelet, improving the current testsuite about coverage and reliability. See for example the April 26 sig-node meeting notes and the [April 27 sig-node CI subgroup meeting notes](http

Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

What happened?

If you don't pass a --name argument to your etcd processes, they will all have the name default and the cluster will operate normally. However, when you add a member, the generated ETCD_INITIAL_CLUSTER variable will have multiple entries with the name "default". When this environment variable is used, etcd will parse these into a mapping under a single key ("defau

expected result:
example.com?param=abc -> will become example.com
example.com/?param=abc -> will stay example.com/

actual result:
example.com?param=abc -> become example.com
example.com/?param=abc -> stays example.com/?param=abc

We already have some scripts in the scripts directory. It would be good to run them for every PR.
This is also a great task for beginners.

https://www.consul.io/docs/agent/telemetry#metrics-reference claims "This is a full list of metrics emitted by Consul." but some are missing:

• The family of new consul.acl.* metrics defined at https://github.com/hashicorp/consul/blob/019aeaa57de97100d57f8ab9c771365b1cfcf7b8/agent/consul/acl_endpoint.go#L33

• consul.consul.cache.entries_count defined at https://github.com/hashicorp/consu

Related kubernetes/minikube#14257

This isn't currently supported, the flag was put in for future proofing to make it easier if we do implement it.

If the user tries to use the flag we should output a message to the user saying the flag is not yet supported and the flag value should be ignored.

 Nacos Server:  2.1.0
 Model: standalone

我启动Nacos server后，启动过程中提示config_info表中缺少encrypted_data_key字段，然后我就手动加了这个字段encrypted_data_key(varchar(255)).但是无法创建新的配置

In the application details view, we list the ports an application deployment is listening on, but there is no "quick launch" or even a "copy" button..

We should add a "copy" button next to the port to copy to clipboard.

Output of helm version:
version.BuildInfo{Version:"v3.8.1", GitCommit:"5cb9af4b1b271d11d7a97a71df3ac337dd94ad37", GitTreeState:"clean", GoVersion:"go1.17.8"}

If HELM_DATA_HOME contains spaces, like `/Users/My Name/Library/hel

It will be useful to install/show helm chart pre releases from a helm repo. Using helm from the commandline pre releases are also not shown or installed. Adding the --devel it will show or install pre releases. It would be nice to have a switch to show the pre releases or not like for example in rancher.
![rancher](https://user-images.githubusercontent.com/106823500/171875868-3c090565-2060-4fcc-a

In what area(s)?

/area runtime

/area operator

/area placement

/area docs

/area test-and-release

Describe the proposal

Today, a PR can break perf tests without maintainers being aware. Running /ok-to-pe

Is your feature request related to a problem? Please describe.
Logs are shown in UTC. IT is frustrating when trying to troubleshoot an issue and need to keep converting timestamps to determine which logs are relevant.

**Describe the sol

Problem: It is pretty challenging to find resource material and valuable articles, videos and such, and we spend a lot of time searching and finding the appropriate resource for us.

Proposed solution: Faceted search can come a long way when looking for a quick way to find a solution designed for our needs. Ratings on the resource can help us select the best solution based on our search

Our parser outputs all aggregations functions using the general sqlparser.FuncExpr. This is a little clunky and requires us to do additional checks before we are sure that the aggregation we have is valid and what it is aggregating.

I suggest we instead introduce one struct type per aggregation, and have them all implement some interface. This would help clean up the code.

Example: