Nowadays, when the kube-scheduler is initialized, the provided component config (via --config flag) is logged. E.g.

I0404 08:35:16.471898       1 configfile.go:96] Using component config
-------------------------Configuration File Contents Start Here---------------------- 
apiVersion: kubescheduler.config.k8s.io/v1beta3
clientConnection:
  acceptContentTypes: ""
  burst: 100
  conten

Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

It's not possible to enable addons with --no-kubernetes passed because the addons in their current state are deployed to Kubernetes. So if a user tries to enable an addon with --no-kubernetes output a message notifying them that it's not possible without Kubernetes and exit execution.

Related kubernetes/minikube#13461

Command helm repo list act differently when repository config file don't exists:

$ helm repo list
Error: no repositories to show
$ helm repo list -o json
[]
$ echo $?
0

$ rm ~/.config/helm/repositories.*

$ helm repo list -o json
Error: no repositories to show
$ echo $?
1

In both cases helm should return return empty list of repositories without exiting with erro

The microsite currently has an (ever growing) menu. When visiting this website on a mobile browser, the menu takes up a lot of space. Also it overlaps text on the page you visit.

Feature Suggestion

If a visitor opens the website on a mobile browser, the menu should not take up a lot

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

Actual the windows executables (jaeger-agent.exe, jaeger-collector.exe, ...) don't have a version set. It is hard to identify the current used version and check if the actual used version is outdated.

Probl

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

Implement WarmPool.RenderTerraform()

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

/kind feature
/area terraform
/lifecycle frozen

Scenario:

• Single vttablet, connecting to external MySQL (happens to be RDS Aurora, but I doubt it matters).
• Single unsharded keyspace (keyspace3), no vschema, with a single table, containing a single row
• Test program using the Python pymysql driver, using the CLIENT.FOUND_ROWS flag, and updating a single row to it's current key value (i.e. no rows are updated, but a single row

Summary

Hi, I'd like to add the annotation cluster-autoscaler.kubernetes.io/safe-to-evict: false to the workflow pod
It will look like

// AnnotationKeyAutoScalerSafeToEvict is the annotation that specify pod is safe to be evicted by autoscaler
AnnotationKeyAutoScalerSafeToEvict = "cluster-autoscaler.kubernetes.io/safe-to-evict"

Annotations: map[string]string{
  c

The idea originated from this comment, see for full context thanos-io/thanos#4908 (comment)

Basically, we could improve the user experience by providing more information on how the stores are being queried, beyond providing just min / max time or just showing that the min / max time is not available, which does not in fact tell users if that store will be que

Add a network option in creating workload

like rancher‘s Networking tab

** During workload creation, user can customize own hosts and DNS search doma

What would you like to be added:

An option/setting for configuring a "retry" of retrieving records specified in secondary/transfer blocks, either with a longer timeout, periodically or until successful (since after that point, the secondary will notify the primary).

Why is this needed:

This supports setups where a name server acts as a DNS entry point who's retrieving records

Description

• If the backend response is missing "Content-Type" header , try to perform MIME sniffing and fix the response header.

Reference

• http://mimesniff.spec.whatwg.org/
• https://github.com/bfenetworks/bfe/blob/develop/bfe_http/sniff.go

Now the helm is related in build, let's move it to root dir.

kubeedge/build/helm -> kubeedge/helm

The library controller-runtime requires setting a logger (by log.SetLogger()) at the first 30s when the application starts, or it would use the default NullLogSink. We should also call it in testing codes.

When we test with ginkgo, ginkgo provides a helpful GinkgoWriter, which hides the output as default, only prints it when the test failed. We'd better use it to keep our testing output

Spent the morning debugging what I thought was a goroutine leak, but turned out to be just a huge number of goroutines being created in a short period of time. However, it seems a lot of the unit tests do leak goroutines. Most of these might just be issues with tests not cleaning up properly, but it makes testing/debugging real leaks quite difficult. Or in my case, the leaks were a red herring - t

Describe the bug

The Version call leaks the GRPC connection, and will remain even after cleaning up the backing manager pods.
https://github.com/longhorn/backing-image-manager/blob/6bcb81541be8c52c0bb543cea357230d37fc87bd/pkg/client/manager_client.go#L173

This is a quick fix and a good chance to have a look at the backing image manager code + interaction patterns.

One can run the long