cncf

What happened:

imagePullSecrets can added to a pod manifest to reference a secret containing registry cre

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?

https://github.com/kubernetes/minikube/blob/9f96701d8f751d5dfce72f2fb762833f4c396747/pkg/minikube/registry/drvs/hyperv/hyperv.go#L94

Get-WmiObject is deprecated and has been superseded by [Get-CimInstance](https://docs.microsoft.com/en-us/powershell/mod

If I define a invalid non local value fine, helm raises a go panic.

helm template examples -f "http://a.b"           
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x54b7018]

goroutine 1 [running]:
bytes.(*Buffer).Bytes(...)
        bytes/buffer.go:54
helm.sh/helm/v3/pkg/cli/values.readFile({0xc0

Requirement - what kind of business use case are you trying to solve?

Actual the windows executables (jaeger-agent.exe, jaeger-collector.exe, ...) don't have a version set. It is hard to identify the current used version and check if the actual used version is outdated.

Probl

GitHub does not show the content (or a diff) of a file larger than a certain size (over 1MB).
Open API Json file could not read location because of size. I have 50 files more than 1 MB.
when we try to register any api from git repo it display following error

`catalog warn Processor PlaceholderProcessor threw an error while preprocessing; caused by Error: Placeholder $text could not read loca

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

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

UI start/end times don't show exact timestamp ie HH:MI:SS . When debugging a failed workflow the exact minute/second is very useful to know.

It seems like the recording rule panel doesn't have the necessary styling applied to it in the dark mode:

Add a network option in creating workload

like rancher‘s Networking tab

** During workload creation, user can customize own hosts and DNS search doma

Is your feature request related to a problem? Please describe.
rovide a method to test/verify if the configuration is correct. before reload the config.
Like nginx -t

Describe the solution you'd like
Simple command.
After run, print the test/verification result.

Describe alternatives you've considered

Additional context

Now we only add part of the configuration info for cloudcore, we can add the full configuration in helm->configmap.

Spent the morning debugging what I thought was a goroutine leak, but turned out to be just a huge number of goroutines being created in a short period of time. However, it seems a lot of the unit tests do leak goroutines. Most of these might just be issues with tests not cleaning up properly, but it makes testing/debugging real leaks quite difficult. Or in my case, the leaks were a red herring - t

Feature Request

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

At present, Dashboard supports setting TTL for archived events and experiments, but schedule and workflow do not. We can extend to this [function](https://github.com/chaos-mesh/chaos-mesh/blob/master/pkg/

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