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.

I think that it would be good user experience if we can add a button besides each code snippet which should be copied to the clipboard like several sites do it.

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

https://travis-ci.com/github/jaegertracing/jaeger/jobs/445878517#L2150

=== RUN   TestReload
    cert_watcher_test.go:110: 
        	Error Trace:	cert_watcher_test.go:110
        	Error:      	Should be true
        	Test:       	TestReload
        	Messages:   	Failed to find wanted logs. All logs: [{{info 2020-11-23 14:13:36.375563204 +0000 UTC m=+0.010957869  Loading modified certif

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

Feature Suggestion

To avoid forgetting to add changesets to certain packages before a release it's best if we can have a GitHub workflow or bot that warns us that a packages is missing changesets. Not all changes to a package would need a changeset, for example a spelling fix in a line comment would not. Because

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

It'd be great to have a frequently asked questions section as part of our official website. Such like https://prometheus.io/docs/introduction/faq/

We are getting similar questions from the community over public slack channels and office hours. We can gather them together and help the community.

cc @bwplotka @brancz

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

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

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