What happened:

I0503 14:20:58.524174   46569 status_manager.go:586] "Patch status for pod" pod="defa

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.

currently in https://github.com/medyagh/minikube/blob/a67a4ccbedd932f184b5713c70498dc434942621/pkg/minikube/bootstrapper/images/images.go#L86
we have

// etcd returns the image used for etcd
func etcd(v semver.Version, mirror string) string {
	// Should match `DefaultEtcdVersion` in:
	// https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/constants/constants.go
	ev := "

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

The PR #2913 opened by dependabot brought a new version of github.com/go-openapi/strfmt, which seems to have a few API incompatibilities with the previous version. This ticket is about making the necessary changes so that we can upgrade to a newer version.

One of the AWS China regions now supports Route53: https://aws.amazon.com/about-aws/whats-new/2020/05/amazon-route-53-is-now-available-in-AWS-china-region/

If someone with an AWS China account can try creating a cluster using Route53 rather than gossip k8s.local and update docs/aws-china.md with their findings that would be much appreciated. Also identify any changes needed to be made in Kops t

When I run "vtctlclient help ApplyRoutingRules", I get informations on how to use this option. But when I run "vtctlclient help GetRoutingRules", I do not get such informations, and it looks like the routing rules are displayed. Output below.

jgagne@ip-172-31-40-211:~/my-vitess-example$ vtctlclient help GetRoutingRules
{

}
jgagne@ip-172-31-40-211:~/my-vitess-example$ vtctlclient hel

Summary

It would be great to add some screenshots of the current PagerDuty plugin to its README here:

https://github.com/backstage/backstage/blob/master/plugins/pagerduty/RE

Prometheus have this from January, it was added to Alertmanager this week too. I think it's time to add it to Thanos too (:

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

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

currently, we have more than one go.mod file, and we should also cleanup these file during make check.

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

We sanitize secrets when they arrive at the cache layer (https://github.com/projectcontour/contour/blob/main/internal/dag/secret.go#L34:6), however, that logic is duplicated in the dag package (https://github.com/projectcontour/contour/blob/main/internal/dag/accessors.go#L225).

I theory we should be able to rely on the secrets being valid from the cache bit, but in any case should centralize t