https://github.com/kubernetes/kubernetes/blob/5bafc8306a7b622e292746aec8a9e9212b755071/staging/src/k8s.io/apimachinery/pkg/runtime/serializer/versioning/versioning.go#L225

I0225 16:19:15.424936 1416311 versioning.go:225] a memory allocator was provided but the encoder %!T(MISSING) doesn't implement the runtime.EncoderWithAllocator, using regular encoder.Encode method

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

It's not possible to enable addons with --no-kubernetes passed because the addons in their current state are deployed to Kubernetes. So if a user tries to enable an addon with --no-kubernetes output a message notifying them that it's not possible without Kubernetes and exit execution.

Related kubernetes/minikube#13461

Command helm repo list act differently when repository config file don't exists:

$ helm repo list
Error: no repositories to show
$ helm repo list -o json
[]
$ echo $?
0

$ rm ~/.config/helm/repositories.*

$ helm repo list -o json
Error: no repositories to show
$ echo $?
1

In both cases helm should return return empty list of repositories without exiting with erro

Feature Suggestion

Make Backstage libraries use the latest version of the jose library.

Context

Dependabot reminds us that it's past due to bump our jose dependency, but their interface has changed pretty significantly. We'd appreciate the help to get that bump done, maybe by a contributor who's familiar with the interface, so

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

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

Summary

As a consequence of one of my PRs, a bug was introduced into the master branch of the Argo Workflows codebase. This had instant repercussions (see Github Issue here) for new users that were consuming the tool. Whenever the docs provide a link to manifests, they point to the master branch (see [here](https://github.com/argoproj/ar

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 the helm is related in build, let's move it to root dir.

kubeedge/build/helm -> kubeedge/helm

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