What would you like to be added:

e2e test for service ExternalIPs

Why is this needed:

There is no test covering Service ExternalIPs

How to test it

Since we can not assume that the e2e binary will have connectivity against the nodes
and that we can add routes to the environment, we are going to test it from a pod.

I've verified that this works locally with the followin

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.

##minikube stop##
vinodhinis-mbp:minikube vinodhinibalusamy$ ./out/minikube stop -p test2
🤷 There is no local cluster named "test2"
👉 To fix this, run: "minikube start -p test2"

this causes unwanted error message thrown in profile list.

vinodhinis-mbp:minikube vinodhinibalusamy$ ./out/minikube profile list
|----------|-----------|---------|--------------|------|---------|---------|
|

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.
I am working on having an alternative OCI runtime on the machines, and currently I can't configure it out of the box with kops so I would need to create an images with dockerd running with alternative runtime and skip docker installation on kops.

There is no runtime configuration for Docker:
https://pkg.go.dev/k8s.

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

Allow people to safely export production traces into GitHub tickets (as a way of reproducing problems, especially with the UI) without exposing sensitive information.

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

The anonymizer is partially implemented.

Proposal - what do you suggest to s

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

When using the backstage-cli create-plugin some build step tasks like yarn tsc might fail. These aren't required to be run and we could handle failures in a more graceful way, simply warning the user that the build task failed.

Current Behavior

If for example yarn tsc fails, the following

What would you like to be added:
Add a new plugin that minimizes responses as describe (e.g.) in the BIND manual

minimal-responses

 minimal-responses yes | no ;
 minimal-responses yes ;

If yes the server will only add records to the authority and additional data sections when they are required e.g. delegations, negative responses. This may improve the performance of the server. T

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

Feature Description

Kubersphere integrate the velero based on the k8s CRD extensions

How does it work
It's like monitoring component

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

https://github.com/cortexproject/cortex/blob/e2a36a7385654cc8b99c646c7f90653ad19ad76c/pkg/chunk/table_manager.go#L340-L350

When the table manager actually attempts to sync and operate on the chunk storage backend it will proceed in the following order:

1. Delete
2. Create
3. Update

If any of these operations fail at any point, the entire sync will return. This can lead to issues for use

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

After #1031, add network delay will also run iptables commands, so we need to test whether they can work together.

Please describe the problem you have

cert-manager made a 1.0 release; upgrade the install and switch the integration test YAML to use the corresponding v1 API resources.