What would you like to be added:

A feature (enabled by default) that any "long running" kubectl command (like exec and logs) send a periodic keep alive signal to the API server.

At this point this is only available for the proxy command where it is disabled by default.

I propose to have this keepalive made a part of also the exec and logs (and others?) and to set the default value to

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

Related issue: kubernetes/minikube#8658

Steps to reproduce the issue:

1. minikube start --apiserver-names=k8s-beta.example.com --apiserver-names=k8s-prod-replica.example.com

Version:

appdelivery@appdelivery-qvm-1:~$ minikube version
minikube version: v1.12.1
c

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

VERSION: v1.14.0
EXPECTATION: single trace response in UI for tag search guid:x-request-id=628d36f4-9072-c587-3b00-804c10a63000

ACTUAL: No trace results. Try another query.
SETUP:

1. To easily get data populated I modified this file `plugin/storage/badger/spans

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

It works in API level: https://thanos.io/tip/components/query/#store-filtering would be nice to have some UI support for it (:

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 happened:
Tried running Regression test using command ./test/run_regression_tests.sh $PWD/build.
The test

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

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 cert-gen job has always used an image tag of :latest to get around the issue of applying the same manifest on top of an existing installation, however, tagged releases use a unique name for each certgen job for that release so there's no need to use latest for releases and can cause issues for users in air-gapped environments.

We should remove the :latest tag and use a specific versio

Feature Request

Is your feature request related to a problem? Please describe:

We can add a new flag such as host-network. If we run install.sh --host-network, install.sh will open hostNetwork for chaos-daemon.

hostNetwork is also defined in [value.yaml](https://githu

Describe the solution you'd like
It would be neat to see the start time of plugins when looking at sonobuoy status. For example, when E2E are running, they may take a while, but when did they start?

$ sonobuoy status                                                                                                            
PLUGIN		STATUS		COUNT
e2e		running		1
systemd_logs	comple

brig build get outputs YAML:

$ brig build get 01ddrty3jt9ns3t7q1zt9t8aym
id: 01ddrty3jt9ns3t7q1zt9t8aym
projectid: brigade-4912ed475391ddbfa05fd2d6e14f59b0fa0acbfe839ebb7d99412a
type: exec
provider: brigade-cli
revision:
  commit: ""
  ref: master
payload: []
script: []
worker:
  id: brigade-worker-01ddrty3jt9ns3t7q1zt9t8aym
  buildid: 01ddrty3jt9ns3t7q1zt9t8aym
  projectid: