The kubelet exposes some metrics HTTP server metrics: https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/server/metrics/metrics.go

However, none of the metrics include response status. Response status metrics are useful for identifying authorization problems, or malformed client requests.

/sig instrumentation
/sig node
/help

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.

Environment:
Minikube on Mac OS X

What happened:

I am trying to load NGINX-Ingress with a custom tls certificate, in this case a trusted TLS certificate I generated on my machine. I start minikube, then enable the ingress-nginx addon which deploys nginx to the kube-system namespace successfully. I create my certificate in the kube-system namespace with the title mkcert.

I then modified

Hello,

According to this thread, it is possible to use some path like file://local/path/to/chart instead of some chart repository URL.

In the documentation, I do not see any examples or mention for this feature.

Can we add it to the documentation or make it more accessibl

1. Describe IN DETAIL the feature/behavior/change you would like to see.
AWS provides this tool for linting cloudformation files:

https://github.com/aws-cloudformation/cfn-python-lint

Running it against our integration test outputs in tests/integration/update_cluster/*/cloudformation.json reports quite a few warnings including mismatched types. It would be great to fix those and addr

Describe the bug
Due to golang/go#16736, the jaeger-agent is unable to setup a connection to a tls grpc reporter endpoint on windows.

Error message:

{"level":"fatal","ts":1602401908.4807255,"caller":"command-line-arguments/main.go:67","msg":"Could not create collector proxy","error":"failed to load TLS config: failed to load CA CertPool: failed to load Syste

Feature Description

MySQL has the ability to configure when to log slow queries with the long_query_time option.

This request is to add similar support for vtgate that will allow vitess admins to configure what they determine are slow queries to be flagged as 'slow'. MySQL uses the SERVER_QUERY_WAS_SLOW flag to indicate this and update statistics.

Use Case(s)

• provi

Feature Suggestion

Based on the conversation in #2709 It would be nice to have a more visual display of lighthouse scores like, lighthouse itself:

Possible Implementation

We could use an array of GaugeProgress elements. Ideally these would be a medium / small size.

Just looked at some man pages and they use 'See Also', not 'Also See' as the reference section. Should probably refer those words in all README.md's and in plugin.md where we detail this.

Feature request

It would be nice to integrate query frontend to the https://github.com/thanos-io/thanos/blob/master/scripts/quickstart.sh so that we can easily test the whole stack.

AC:

1. In-memory result cache config should be supported
2. Would be nice to configure Jaeger for query frontend

Background

• BFE can be configured with Passive Health Check (i.e. Outlier Detection) and use responses from real requests to determine whether an backend instance is healthy.

Description
Add Active Health Check support:

• Actively and periodically send health checking requests to backend.
• Use responses from health checking requests to determine whether an backend instance is he

@bwplotka introduced a new streaming remote read in Prometheus, we should add the same to Cortex for people who point Prometheus and Thanos at Cortex.

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

What happened:
Tried running Regression test using command ./test/run_regression_tests.sh $PWD/build.
The test

I’ve got an interesting use case where we are using VK to manage binary workloads running on client machines. We like the idea of taking advantage of the scheduler, secret management and “pod” status tracking while bootstrapping our own use case into the system.

The hang up right now is that VK authenticates with a master using a kubeconfig file, which is obviously not something we can put on a c

Please describe the problem you have

Run the linter from the Github action for better PR integration

https://github.com/golangci/golangci-lint-action

bonus points if we can add this to https://github.com/projectcontour/.github/ in such a way that every repo gets it automatically.

Many kinds of chaos are sharing the same Recover logic. A typical Recover function is like below:

func (r *Reconciler) Recover(ctx context.Context, req ctrl.Request, obj v1alpha1.InnerObject) error {

	podchaos, ok := obj.(*v1alpha1.PodChaos)
	if !ok {
		err := errors.New("chaos is not PodChaos")
		r.Log.Error(err, "chaos is not PodChaos", "chaos", obj)
		return err
	}

	if er