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.

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

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

In the application details view, we list the ports an application deployment is listening on, but there is no "quick launch" or even a "copy" button..

We should add a "copy" button next to the port to copy to clipboard.

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

https://leapgraph.com/graphql-api-security

This article mentions several add-on packages that Reaction may want to use. This issue is simply to investigate whether these vulnerabilities are present and try adding the packages to solve them.

This is a request for implementing the --post-render flag in helm to be able to execute things like:
helm install mychart stable/wordpress --post-renderer ./path/to/executable
In particular the aim is to use kustomize as a followup of the helm.

Expected behavior

a key to be added to the helm's deploy

Actual behavior

No such option

Information

• Skaffold version: NA

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.