When we first added SCTP tests, we thought that we weren't going to be able to do actual tests of SCTP network connectivity within kubernetes CI, so we came up with a plan involving a split between tests that involve actual SCTP network connectivity (which require the SCTP kernel module to be available) and tests that don't do SCTP network traffic and so can run anywhere. That way we could still t

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.

Steps to reproduce the issue:

1. Download amd64 debian package of latest release: https://github.com/kubernetes/minikube/releases/download/v1.16.0/minikube_1.16.0-0_amd64.deb
2. Inspect the package file
3. It's marked as an arm64 package not an amd64 package
4. It has stray files in it that are c

Helm documentation states the following:
-1) (k8s) metadata.name is restricted to a maximum length of 63 characters because of limitations to the DNS system
-2) For that reasons, release names are (DNS labels that are) limited to 53 characters

Statement 1) is not correct.
k8s does not impose a max length of 63 characters on resource names.
The actual max length for a resource name is 253 c

Split from jaegertracing/jaeger#2645 to track the work in other repos:

• jaeger-lib jaegertracing/jaeger-lib#85
• jaeged-idl jaegertracing/jaeger-idl#68
• jaeger-operator
• jaeger-client-java jaegertracing/jaeger-client-java#765
• jaeger-client-go https://githu

1. Describe IN DETAIL the feature/behavior/change you would like to see.

Using AWS GovCloud is a bit different from the regular AWS.
https://github.com/kubernetes/kops/blob/master/docs/getting_started/aws.md

2. Feel free to provide a design supporting your feature request.

Kops v1.18.2 improves the support for AWS GovCloud and should work without any additional tweaks, except for

Problem Statement

There are users who would like to secure the http port exported by the vitess servers with TLS. However, some of the health check and monitoring URLs (like /debug/vars) still need to be accessed without TLS. For example, Kubernetes prefers the health check URLs to not require TLS.

We require the ability to specify a separate (optional) TLS http port, and the ability to s

There's some wrong category lables in the Plugin Marketplace.

AWS Lambda and Firebase Functions could be Infrastructure instead or something better than monitoring at least.

The word is used in lots of places, e.g.:
https://thanos.io/tip/thanos/design.md/ "Chunk files hold a few hundred MB worth of chunks each."
https://thanos.io/tip/thanos/storage.md/ "This can be used to find chunk with samples in the chunk files."

It would be good to define it, like "a chunk is part of the data structure of Prometheus TSDB, holding up to 120 samples for a single timeseries".

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 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

There are a few things I noticed while following @codesome's Rawkode podcast: https://www.youtube.com/watch?v=lI-4jHKv2Y0

• People need to install Golang, and compile Cortex/Prometheus for them to run through the getting started guide. This is not trivial at all even for Prometheus, we need to install node and yarn for asset compilation. We should be using release binaries instead.

• **P

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

There is no e2e test and documents for external network delay and partition now 🤦 .

The e2e test could be found in /test/e2e/chaos/basic.go. Reading other tests in that file could help accomplish this issue.

Example for extern network delay:

apiVersion: chaos-mesh.org/v1alpha1
kind: NetworkChaos
metadata:
  name: network-netem-example
  namespace: chaos-testing
spec:

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

klogv2 has the https://godoc.org/github.com/kubernetes/klog#SetLogger API, which should let us drop the vaguely sketchy output stream we use to capture core Kubernetes log output.