The folks maintaining the Rust Kubernetes API client have noted some discrepencies in our spec. Details are here:

• https://github.com/Arnavion/k8s-openapi#works-around-bugs-in-the-upstream-openapi-spec
• https://github.com/Arnavion/k8s-openapi/blob/master/k8s-openapi-codegen/src/fixups/upstream_bugs.rs
• https://github.com/Arnavion/k8s-openapi/blob/master/k8s-openapi-codegen/src/supported_ve

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.

docker does not allow volume names shorter than 2 letters.
which will cause minikube to crash on docker driver

medya@~/workspace/minikube (docker_network) $ ./out/minikube start -p p
😄  [p] minikube v1.13.1 on Darwin 10.15.6
✨  Automatically selected the docker driver. Other choices: hyperkit, virtualbox
👍  Starting control plane node p in cluster p
🔥  Creating docker container (CPU

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

We should consider standardizing our Event API to follow CNCF's https://cloudevents.io/ standard.

Benefits: better alignment with the space, standardized format which aligns better with best practices
Cons: IDEs will need to restructure their clients

Thoughts?

Environment:

• Jib version: 2.5.0
• Build tool: Gradle 6.5.1 (Kotl

What would you like to be added:
Sometimes pod is killed by various reason, but the reason is not visible in Lens. I need to execute kubectl command to see last state and reason why the pod was killed

State:          Waiting
  Reason:       CrashLoopBackOff
Last State:     Terminated
  Reason:       OOMKilled
  Exit Code:    137
  Started:      Tue, 15 Sep 2020 08:45:37 +0200

Add a performance test that measures the time it takes Dapr to save data into a state store.

The important piece that is being tested is the processing that Dapr does before saving to the state store. This test should not benchmark the component itself.

For that purpose, a baseline test scenario would have an app that saves a 1kb payload to Redis, followed by a test app that uses Dapr to sav

A relative path can be specified for --root, but it is sometimes interpreted as relative to current directory and sometimes as relative to bundle directory:

> sudo find .
.
./mybundle
./mybundle/config.json
./myroot
> sudo runc --root myroot create --bundle mybundle a
> sudo find .
.
./mybundle
./mybundle/config.json
./mybundle/myroot
./mybundle/myroot/a
./mybundle/myroot/a/exe

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

https://www.eclipse.org/che/getting-started/cloud/ list things like thorntail which is no longer supported - could it be replaced with a Quarkus flow ?