What happened:

When using Graceful Node Shutdown feature, status and reason of "shutdown" pod are confusing for users. See kubernetes/website#28235 where I attempt to address this confusion by documenting the behavior.

However, it would be great to improve messages. Perhaps the following renaming:

Status:         Failed. --------------------------------

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 was dong a mistake and put wrong k8s version, we should have a more beautiful looking error, and ideally do not even try to create container when a non-existing k8s version is specified

mk start --kubernetes-version=20.10.7
😄  minikube v1.21.0-beta.0 on Darwin 11.4
✨  Automatically selected the docker driver. Other choices: hyperkit, parallels, virtualbox, ssh
👍  Starting control plane 

Output of helm version:

Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

Output of kubectl version:

Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.7", GitCommit:"d

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

Hello team, in PR jaegertracing/jaeger#2798 the tls connection is enabled in collector, it would be good to support configuring cipher for it.

It would be similar to the fluentd tls settings in https://docs.fluentd.org/configuration/transport-section#tls-setting, you can config the ciphers fi

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

Feature Suggestion

If the new search result page returns no result, the result list is only empty. There is no difference between "loading" and "no results" - which might confuse the user.

Pos

Since we've upgraded our ProtoBuf package version in vitessio/vitess#8075, the new serializer to JSON and ProtoText inserts random whitespace on its output that prevents byte-wise comparison.

Our test suite makes extensive use of "golden tests" that compare these outputs. In order to complete the upgrade successfully, I had to disable the randomness in the serializer.

Is your proposal related to a problem?

Moving from Prometheus to Thanos and I am now noticing that Ruler does not show alert rule duration in the UI like Prometheus would show. I think it is important to show this

I have been asked several times whether the value filled in cc.spec.common.es.externalElasticsearchUrl requires an http prefix, but it is actually not needed, but this key is a bit confusing. I don’t know if I need an http prefix sometimes when I look at it, so I think it’s clearer to change it to externalElasticsearchUrl to externalElasticsearchHost

/kind feature-request

Description

• Upgrade go version from 1.13 to 1.16

Some of our tests are slow. Here is list of packages with tests that run above 5 seconds (from https://github.com/cortexproject/cortex/runs/2054589567 run).

227.510s    github.com/cortexproject/cortex/pkg/ring
213.005s    github.com/cortexproject/cortex/pkg/querier
60.907s github.com/cortexproject/cortex/pkg/ingester
60.674s github.com/cortexproject/cortex/pkg/storegateway
42.779s gith

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

refs to https://pkg.go.dev/sigs.k8s.io/controller-runtime/pkg/envtest#pkg-constants, the actual usful env is USE_EXISTING_CLUSTER not TEST_USE_EXISTING_CLUSTER, and we have used the former for a while. 😰

i am cloning this git repository into the path /root/src/github.com/
my GOPATH=/root/src/
my GOROOT=/root/
my GOBIN="/root/src/github.com/virtual-kubelet/bin"
and i enter /root/src/github.com/virtual-kubelet directory and run the make build command, i get this error:

`which: no gobin in (/bin:/root/src/github.com//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/usr/loc

What steps did you take and what happened:
Consider the following setup
I created a manifest based on the latest example contour yaml.
The difference is running the shutdown-manager container as a non root user, in a container with readOnlyFilesystem is true.

    securityContext:
      runAsUser: 154691
      runAsGroup: 154691
      allowPrivilegeEscalation: false