Just noticed that we have redundant metrics for watch counts like:

# HELP apiserver_longrunning_gauge [ALPHA] Gauge of all active long-running apiserver requests broken out by verb, group, version, resource, scope and component. Not all requests are tracked this way.
# TYPE apiserver_longrunning_gauge gauge
apiserver_longrunning_gauge{component="apiserver",group="",resource="configmaps",

Feature idea summary

Cgroups plugin supports only proportional and max Block IO policies. We should support BFQ scheduler as well. Disk stats for the scheduler are in blkio.bfq.io_service_bytes and blkio.bfq.io_serviced files.

currently our make generate-docs creates this page

https://minikube.sigs.k8s.io/docs/contrib/tests/

which generates the site based on the Comments on the Test and validate the func,

I would like these descriptions to exaclty say what it is doing instead of a general text

validateBuildImage 
makes sures that

Output of helm version:

Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

Output of kubectl version:

Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.7", GitCommit:"d

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

Hello team, in PR jaegertracing/jaeger#2798 the tls connection is enabled in collector, it would be good to support configuring cipher for it.

It would be similar to the fluentd tls settings in https://docs.fluentd.org/configuration/transport-section#tls-setting, you can config the ciphers fi

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

Since we've upgraded our ProtoBuf package version in vitessio/vitess#8075, the new serializer to JSON and ProtoText inserts random whitespace on its output that prevents byte-wise comparison.

Our test suite makes extensive use of "golden tests" that compare these outputs. In order to complete the upgrade successfully, I had to disable the randomness in the serializer.

I am referring to an issue, which is very similar to backstage/backstage#5577. It is related to the scaffolder-backend plugin.

In our company, we are running a self-hosted Bitbucket repository. It can be accessed via https://code.mycompany.com/bitbucket/. Therefore the base path for APIs is at https://code.mycompany.com/bitbucket/rest/api/1.0/ (note the /bitbucket/ in

Is your proposal related to a problem?

Replication is currently slow.

Describe the solution you'd like

tools bucket replicate could upload a few objects at a time instead of one by one

Describe alternatives you've considered

Copying the objects with some other tool but tools bucket replicate is way too convenient because you can use two completely different object st

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

Description

• Upgrade go version from 1.13 to 1.16

There are a few things I noticed while following @codesome's Rawkode podcast: https://www.youtube.com/watch?v=lI-4jHKv2Y0

• People need to install Golang, and compile Cortex/Prometheus for them to run through the getting started guide. This is not trivial at all even for Prometheus, we need to install node and yarn for asset compilation. We should be using release binaries instead.

• **P

What would you like to be added/modified:

To improve project stability, we need more tests to cover corner cases.
And the code coverage is around 50% currently, we need to add more tests to improve it.

To improve case coverage, we may need a list of cases to track the work.
For code coverage, simply check bef

Bug Report

What version of Kubernetes are you using?

ParseNamespacedName and ParseNamespacedNameContainer functions don't check the length of the parts array before using it, which may panic the whole program when using these two functions https://github.com/chaos-mesh/chaos-mesh/blob/master/controllers/utils/controller/key.go#L22-L36

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

There are a few instances within the docs which still have artifacts left over from the Jekyll to Hugo migration. These instances have all been fixed in v1.15.1 and main, but still remain in previous versions.

This will be a tracking issue for the fixes, so if you want to just fix part of the list please do so and reference this issue.

The list below shows how the artifacts impact the v1.15.