Kubernetes

Which jobs are flaking?

we saw this in a sig-windows test today, blob:https://prow.k8s.io/789c15e1-3869-4a8a-b8ef-ef8394f5be0a

from this family

https://testgrid.k8s.io/sig-windows-1.22-release#aks-engine-windows-dockershim-1.22

Jul 10 02:49:49.489: INFO: Pod statscollectiontest-69785fa8-1d35-4253-a720-9c8acc39c08a-1 is Failed, but it's not controlled by a controller
Jul 1

Bug description

netdatacli has limit for output size of 4096

Expected behavior

do we just increase this limit or make it transfer arbitrary message sizes?

What happened?

In a Jepsen test run of five etcd 3.5.3 nodes, with process pauses (sending processes SIGSTOP and SIGCONT), compaction (performed via the admin API), and defragmentation (via etcdctl), one etcd process crashed with the following error message:

{"level":"panic","ts":"2022-06-13T14:11:27.870Z","caller":"etcdserver/apply.go:638","msg":"unexpected error during txn","error

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.

So pretty weird issue:
I am creating 2 prefixes, one empty, one not empty like this...

consul kv put testprefix/
consul kv put testprefix2/testkey

then when I curl those prefixes recursively like:

curl localhost:8500/v1/kv/testprefix?keys
# this is the reply -> ["testprefix/","testprefix2/testkey"]

notice how only testprefix/ is specifically listed?

now

What Happened?

I noticed on our examples on website does not have Arm64 support yet
and when you try to curl the Service URL or open it in the browser it fails.

the real problem was the pod was crashing but minikube still gave me a URL

$ kc get pods 
NAMESPACE     NAME                               READY   STATUS             RESTARTS      AGE
default       hello-minikube-5c5f5cd

官网介绍描述错误
官网菜单
nacos2.0
升级文档
启动服务器

这部分描述使用内嵌数据库模式下，单机和集群的启动命令一摸一样 。是不是错误了

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.

In multiple places, Helm uses the term "table" when describing the destination for a value. Example:

https://github.com/helm/helm/blob/db2485b20c8f53d802f4fc98c2f95e1fc0460d15/pkg/chartutil/coalesce.go#L222-L224

Error seen:

jbanasik@akira:~/k8s/loki$ helm install cassandra bitnami/cassandra --namespace loki -f cassandra.values.yaml
coalesce.go:223: warning: destination for cassandra

Pod tolerations number is sticked to the start of the line, causing text overflow.

The feature ask - expose Dapr runtime version in the Metadata API: https://docs.dapr.io/reference/api/metadata_api/

There are certain scenarios where apps would like to check that they are running within a tested Dapr version.

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