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.

Today, etcdctl endpoint health only performs a quorum GET. If server is corrupted or exceeded quota (which put the server into read only mode), this command incorrectly returns healthy.

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

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

Move all Dockerfile samples to non-root user

Expected Behaviour

As an OpenFaaS end-user, I want to run all samples on my OpenFaaS cluster, even with the new non-root feature enabled.

Current Behaviour

Hello,

According to this thread, it is possible to use some path like file://local/path/to/chart instead of some chart repository URL.

In the documentation, I do not see any examples or mention for this feature.

Can we add it to the documentation or make it more accessibl

Issue Description

Type: bug report

Describe what happened

java.lang.IllegalStateException: failed to req API:/nacos/v1/ns/instance/beat after all servers([minion-register:8848]) tried: failed to req API:minion-register:8848/nacos/v1/ns/instance/beat. code:400 msg: java.lang.IllegalArgumentException: dom name can only have these characters: 0-9a-zA-Z-._:, current: DEFAULT_GROU

Feature Description

MySQL has the ability to configure when to log slow queries with the long_query_time option.

This request is to add similar support for vtgate that will allow vitess admins to configure what they determine are slow queries to be flagged as 'slow'. MySQL uses the SERVER_QUERY_WAS_SLOW flag to indicate this and update statistics.

Use Case(s)

• provi

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

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

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:
Support for deploying vSphere storage Container Storage Interface (CSI).
It' GA already.

https://github.com/kubernetes-sigs/vsphere-csi-driver
https://cloud-provider-vsphere.sigs.k8s.io/

It requires vSphere 6.7u3+

Why is this needed:

• The in-tree cloud provider for vSphere is deprecated.
• The CSI is the standard way to implement the Storage

Every kubeflow image should be scanned for security vulnerabilities.
It would be great to have a periodic security report.
Each of these images with vulnerability should be patched and updated.

Is your feature request related to a problem? Please describe.
As a user I often update apps by simply changing their image tag... edit the yaml is a tedious task.

Describe the solution you'd like
I would love to see a quick set im

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