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.

Environment:
Minikube on Mac OS X

What happened:

I am trying to load NGINX-Ingress with a custom tls certificate, in this case a trusted TLS certificate I generated on my machine. I start minikube, then enable the ingress-nginx addon which deploys nginx to the kube-system namespace successfully. I create my certificate in the kube-system namespace with the title mkcert.

I then modified

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

In scale deployment popup screen, please add + and - buttons near by slider. This will be an easy to use case. Thanks

Describe the proposal

Upgrade Golang Lint to 1.30.0

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 ?