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.

minikube start does not support the MINIKUBE_ADDONS environment variable as a proxy for the --addons argument as it does with other options.

Steps to reproduce the issue:

1. MINIKUBE_PROFILE=this-works MINIKUBE_ADDONS=registry minikube start
2. `MINIKUBE_PROFILE=this-works minikube addon

Any hover effects doesn't properly applied to all header elements (top line with cluster name and cluster menu). It seems that something placed on top of them and covers most of their height.

https://user-images.githubusercontent.com/9607060/108056014-cd186a00-7061-11eb-8ac0-5d01e206e636.mp4

In what area(s)?

/area test-and-release

Describe the proposal

Currently before each rc release

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

Description

runsc install is able to edit /etc/docker/daemon.json to enable Docker to replace runc with runsc.
Would be great if podman supports this feature.

Is this feature related to a specific bug?

No. By the way, does gVisor depend on Docker just for the reason that Docker uses runsc as its runtime?

Do you have a specific solution in mind?

To replace the runtim

The typescript sample project does not compile the .ts files when ENV is production.

When ENV=development, tsc-watch compiles the code in place before starting node. However, there is no corresponding compile step when ENV=production.

Not a huge deal, as only the dev profile is defined, but I think the README should mention that the compile step is missing when ENV=production.

Environment:

• Jib version: 3.0.0
• Build tool: maven 3.6.3,Java version: 1.8.0_282,
• OS: ubuntu20.04

Description of the issue:
mvn clean compile jib:build not work for war project.
have to package the war project. mvn clean package jib:build
The documents and the log output do not mention that.

Expected behavior:
work as jar project.

**Steps to re

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 `*