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.

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

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

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

This is a reminder for me or a task if anyone wants :P

Basically, The last two questions aren't really regex's questions.

To do:

• Move said questions to correct place.
• Add new regex questions (Python related!)?
• Maybe add a new ## Regex section, as it is a valuable skill

There are a lot of places in libcontainer/cgroups/fs where the usage of writeFile function can be optimised. For example here https://github.com/opencontainers/runc/blob/master/libcontainer/cgroups/fs/blkio.go#L44-L51
the function call to writeFile is made for each entry in the slice BlkioWeightDevice, which in turn opens and closes file for each entry. This can be optimised by joining al

Currently, Trivy traverses all paths and looks for all Gemfile.lock in a container image. However, the image sometimes has only Gemfile.lock and doesn't install gems listed in the Gemfile.lock. I think a gem should have *.gemspec file if it is installed. e.g. rake.gemspec has the information about rake.

To avoid false positives from Gemfile.lock, we are probably able to take advantage of `*