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

The PR is #4008

Last time I tried to get this working, the issue was with getting python.d
to properly load the Yoctopuce modules. As far as I could tell at the time, the dynamic import thing works, it's just an issue with getting Python to properly import modules that aren't in system.path, but I didn't look very deep beyond that. Part of the problem there is that the Yoctopuce Python

This is required for #9156

Switching from https://github.com/kubernetes/klog to https://github.com/google/glog should be easy, as klog is a newer fork of glog. klog supports the ability to specify log destinations, which is why it is important for #9156

This should be achievable mostly a search & replace of glog to klog, but initialization is slightly different. See this PR I proposed &

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

Expected Behavior

• Status indicator on the each build step is correct colour and status text

Current Behavior

• When the build fails each build step is listed as Completed with a green status mark

Possible Solution

• Update the status text and colour to reflect a more realistic status

Steps to Reprodu

*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