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://

Hi, I am using minikube v1.18.1 on Hyper-V (Microsoft Windows 10 Enterprise)
I recently tried to uninstall minikube and reinstall it.

Steps to reproduce the issue:

1. I remove the .minikube directory manually (I know I shouldn’t have), only one file remain : a snapshot file .vmcx, probably the configuration file of my previous VM.
2. I added a new Hyper-V switch under the "virtual

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

Beta release: Grayscale release can not select client IP needs to be filled in manually, hope to add support to select IP directly from the connected client
Beta发布: 灰度发布不能选择客户端ip 需要手动填写，希望增加支持从已连接的客户端直接选择ip

Describe the bug
When selecting "Help" -> "Documentation" Lens navigates to https://docs.k8slens.dev/ but should navigate to the documentation corresponding to the running version (e.g. https://docs.k8slens.dev/v4.1.0/).

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

In what area(s)?

/area test-and-release

Describe the proposal

Currently before each rc release

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.

[email protected]:~/my-vitess-example$ vtctlclient help GetRoutingRules
{

}
[email protected]:~/my-vitess-example$ vtctlclient hel

https://github.com/verdaccio/monorepo/blob/9.x/core/types/index.d.ts defines

type AuthAccessCallback = (error: string | null, access: boolean) => void;

interface IPluginAuth<T> extends IPlugin<T> {
  authenticate(user: string, password: string, cb: AuthCallback): void;
  adduser?(user: string, password: string, cb: AuthCallback): void;
  changePassword?(user: string, password: stri

Currently validating checksums requires lots of knowledge on the part of the caller. We should expose optional checksum validation in our existing validation functions e.g. IPv4.IsValid.

header.UDP and header.TCP don't currently have these functions; we should add them.

The container-debug-support images uses skaffold build to build and test images. These builds don't have a cluster available and so a plain skaffold build causes Skaffold to attempt to build and push images, which fails. So we explicitly configure build.local.push: false so that the images are only built to the local Docker daemon.

Environment:

• Jib version: 2.8.0
• Build tool: Maven 3.6.1
• OS: Windows 10

Description of the issue:
Setting environment entries to an empty string results in the following message:

Execution default-cli of goal com.google.cloud.tools:jib-maven-plugin:2.8.0:dockerBuild failed: environment map contains null values 

Expected behavior:
The ENV variable

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

/kind feature

This is a sub-issue from #5494.
We need to remove any f"strings" from the backend of the Jupyter web app in order to be able to use lower versions from Python 3.6 to run it.

/good-first-issue