grep -nr '/enhancements/keps/' * | grep -v '^vendor' | grep -v '/README.md' | grep -v '.json' | grep -v '.pb.go' | grep -v '.proto' | grep -v 'generated'

• OWNERS_ALIASES:581: # conformance aliases https://git.k8s.io/enhancements/keps/sig-architecture/20190412-conformance-behaviors.md
  #101009
• pkg/apis/core/types.go:2835: // More info: https://git.k8s.io/enhancements/keps

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.

"found" by the @discordapp troops the hard way: https://status.discordapp.com/incidents/62gt9cgjwdgf
pinging @zorkian who pointed it out to me.

trivial to repro, this is against a 3.3.13 on fedora-31.

$ etcdctl set /baa schnorp
$ etcdctl get /baa
schnorp
$ echo -ne 'PUT /v2/keys/baa HTTP/1.1\r\nHost: boo\r\nContent-Length: 123\r\n\r\n' | nc localhost 2379
HTTP/1.1 200 OK
...
$ et

Next line returns 200 as status https://github.com/Kong/kong/blob/c817fada7a514d84f6e0aab7461605c71bf3a841/kong/plugins/cors/handler.lua#L13

Internet says it should return 204:

• https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request
• https://docs.microsoft.com/en-us/aspnet/core/security/cors?view=aspnetcore-3.1#preflight-requests

Internet changed its mind since 2018 https://

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

Issue Description

Type: feature request

Describe what happened (or what feature you want)

Describe what you expected to happen

When Dubbo is registered, it is registered according to the interface. If you want to logoff all interfaces provided by a service. It's too painful to search for only one interface, then enter the details, and then go offline. If you can provide a qu

What would you like to be added:
I'd like the node view to show ALL allocatable resource on the node, not just the basic CPU/mem/pod amounts.

Why is this needed:
In many cases kubelet reports devices, hugepages etc. as usable resources and having to dive into node yaml via edit button is, eh, bad experience. :)

![Screenshot 2021-05-12 at 16 23 40](https://user-images.githubuser

In what area(s)?

/area runtime
/area operator
/area placement
/area docs
/area test-and-release

What version of Dapr?

1.1.x
1.0.x
edge: output of `git describe

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

Describe the bug

I've built the verdaccio/verdaccio:local local image (Windows 10 latest, Docker Desktop) but cannot build the v4/5 reverse_proxy docker-examples.

To Reproduce

1. cd verdaccio && pnpm docker

2. cd verdaccio\docker-examples\v4\reverse_proxy\nginx\relative_path\ OR
   cd verdaccio\docker-examples\v5\reverse_proxy\nginx_relative\

3. docker-compose up

Description

While writing a PacketImpact test for ICMP sockets, I found a discrepancy with Linux.

When binding to the following IPv6 multicast addresses,

• ff01::1
• ff02::1
• ff02::2

Linux returns the EINVAL error code, but gVisor returns the EADDRNOTAVAIL error code.

Steps to reproduce

1. Run test `//third_party/gvisor/test/packetimpact/tests:icmp_bind_nati

Expected behavior

The ability to specify the driver to container-structure-test.

Actual behavior

The docker driver is always used (container-structure-test default).

Information

• See [container-structure-test documentation](https://github.com/GoogleContainerTools/cont

Environment:

• Jib version: 2.7.1
• Build tool: Maven
• OS: N/A

Description of the issue:

Invoking mvn jib:help results in error

[ERROR] Could not find goal 'help' in plugin com.google.cloud.tools:jib-maven-plugin:2.7.1 among available goals _skaffold-fail-if-jib-out-of-date, _skaffold-files-v2, _skaffold-init, _skaffold-package-goals, _skaffold-sync-map, build, 

FEATURE REQUEST:
Hi,

I see that there is nothing in the kargo repo related to docker login stuff and more precisely nothing about the ability to make kubernetes pull images from private registries such as ECR.

I have a solution for this that currently works for ECR and CoreOS and that could be extended to different registries solutions (azure one, custom private registry on premi