The folks maintaining the Rust Kubernetes API client have noted some discrepencies in our spec. Details are here:

• https://github.com/Arnavion/k8s-openapi#works-around-bugs-in-the-upstream-openapi-spec
• https://github.com/Arnavion/k8s-openapi/blob/master/k8s-openapi-codegen/src/fixups/upstream_bugs.rs
• https://github.com/Arnavion/k8s-openapi/blob/master/k8s-openapi-codegen/src/supported_ve

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.

docker does not allow volume names shorter than 2 letters.
which will cause minikube to crash on docker driver

medya@~/workspace/minikube (docker_network) $ ./out/minikube start -p p
😄  [p] minikube v1.13.1 on Darwin 10.15.6
✨  Automatically selected the docker driver. Other choices: hyperkit, virtualbox
👍  Starting control plane node p in cluster p
🔥  Creating docker container (CPU

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

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

High availability and resiliency of Jaeger in production environments

Problem - what in Jaeger blocks you from solving the requirement?

Currently, the official images for jaeger are on docker hub. Unless one has a docker paid account, image pulls will be rate-limited and pulls may fail at run-time, causing infrastr

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

Cloud costs should be tied to the software catalog entities that incurred the cost.

Possible Implementation

Update Entity in cost-insights to use Entity from the catalog plugin.

Context

Cost Insights currently has its own Entity definition; this should instead reference catalog entities where possible. This will enable cloud costs to be shown on pages for

*Thanos, Prometheus and Golang version used

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

The argoci docs have a section on how to configure an ingress controller. We should add a Contour section to show users who want to use Contour, what setup needs done.

https://argoproj.github.io/argo-cd/operator-manual/ingress/

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