What would you like to be added?

The changes to support snapshot tests for Generic Ephemeral Volumes kubernetes/kubernetes#105659 generated some duplicated code in the file test/e2e/storage/testsuites/snapshottable.go as commented here: kubernetes/kubernetes#105659 (comment), it'd be great to create functions that are reused in b

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

Steps to reproduce the issue:

1. minikube -p p1 start and wait for cluster p1 to be ready => minikube created network 6775a57b0a2c p1 bridge local
2. minikube -p p1 stop => cluster stop, network p1 still exists (as expected)
3. minikube -p p2 start and wait for cluster p2 to be

Reduce repetitive oci format verification logic
replace strings.HasPrefix(repoURL, "oci://") by registry.IsOCI

Output of helm version:
helm v3.7.1
Output of kubectl version:
None
Cloud Provider/Platform (AKS, GKE, Minik

To complete the issue #2749, there's one PR that needs some attention: #2850. At its current state, it adds the contents of the Jaeger UI build to a Go asset in an uncompressed format. This causes an increase of approximately 10MB to the binary size of the Query/all-in-one.

Ideally, we'd find a way to store the contents of the UI in a compressed format in the binary and serve the compressed ass

1. Describe IN DETAIL the feature/behavior/change you would like to see.

Implement WarmPool.RenderTerraform()

2. Feel free to provide a design supporting your feature request.

/kind feature
/area terraform
/lifecycle frozen

Feature Suggestion

Allow users of the Gauge component to opt out of the 'traffic light' colour-selection by just passing an explicit colour as a prop.

Possible Implementation

Add a prop for color to the component. If present, simply set that as the strokeColor of the Circle component, otherwise do the palette lookup as currently implemented.

Context

We have a use c

Scenario:

• Single vttablet, connecting to external MySQL (happens to be RDS Aurora, but I doubt it matters).
• Single unsharded keyspace (keyspace3), no vschema, with a single table, containing a single row
• Test program using the Python pymysql driver, using the CLIENT.FOUND_ROWS flag, and updating a single row to it's current key value (i.e. no rows are updated, but a single row

These are all functions/structs for configuring the same thing:

https://github.com/thanos-io/thanos/blob/5bda2d48b9ef0bf138af6132641eb20102223edb/pkg/objstore/azure/helpers.go#L121
https://github.com/thanos-io/thanos/blob/46ac4d590e783368fc4ec7676f29ff97cd0bd630/pkg/objstore/cos/cos.go#L95
https://github.com/thanos-io/thanos/blob/bf963237e0b95402aeea4093dce465abde055675/pkg/objstore/s3/s3.go#

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

I have been asked several times whether the value filled in cc.spec.common.es.externalElasticsearchUrl requires an http prefix, but it is actually not needed, but this key is a bit confusing. I don’t know if I need an http prefix sometimes when I look at it, so I think it’s clearer to change it to externalElasticsearchUrl to externalElasticsearchHost

/kind feature-request

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
In some situation, like XiaoDu watch, which is sensitive to power consumption, may need to close the TCP-KeepAlive heartbeat message or increase the interval to send TCP-KeepAlive heartbeat message.
Mod_tcp_keepalive can help handle situ

In this document, following sentence has a typo,

# Register the intrumentation handlers (/metrics etc).

intrumentation -> instrumentation

# Register the instrumentation handlers (/metrics etc).

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

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

There are not enough logs in the backend of Chaos Mesh Dashboard.

For example:

https://github.com/chaos-mesh/chaos-mesh/blob/d0dcca20ddf6da79cf4c2bdb682656f0617c24c3/pkg/apiserver/archive/archive.go#L163-L173

When an error occurs, the detail of the error is only introduced in the HTTP response. It

i am cloning this git repository into the path /root/src/github.com/
my GOPATH=/root/src/
my GOROOT=/root/
my GOBIN="/root/src/github.com/virtual-kubelet/bin"
and i enter /root/src/github.com/virtual-kubelet directory and run the make build command, i get this error:

`which: no gobin in (/bin:/root/src/github.com//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/usr/loc

We want to have consistent and structured logs to improve the ability to filter and analyse longhorn-manager logs.
Currently the controller uses the global logrus package logger, the task here would be to switch the log calls to the instance logger that was implemented in longhorn/longhorn-manager#661

While doing this also improve the log messages, where possible.
For an example of a successf