Follow-up of kubernetes/kubernetes#98241 (comment). Currently we maintain a local registry for looking up the ClusterEvent obj by specifying a cluste event (string). The registry is not that necessary as we can build that ClusterEvent obj on the fly in movePodsToActiveOrBackoffQueue().

/kind cleanup
/sig scheduling

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.

"found" by the @discordapp troops the hard way: https://status.discordapp.com/incidents/62gt9cgjwdgf
pinging @zorkian who pointed it out to me.

trivial to repro, this is against a 3.3.13 on fedora-31.

$ etcdctl set /baa schnorp
$ etcdctl get /baa
schnorp
$ echo -ne 'PUT /v2/keys/baa HTTP/1.1\r\nHost: boo\r\nContent-Length: 123\r\n\r\n' | nc localhost 2379
HTTP/1.1 200 OK
...
$ et

Summary

We're starting up kong for integration tests for our custom plugins using the start_kong method implemented in spec/helpers.lua. We need to be able to set environment variables as our plugin is using some custom environment variables. Currently the only way through the start_kong method to set env vars is to prefix them with KONG_. I noticed that kong_exec, which start_kong calls ha

here we confuse the user with two things

❗ You cannot change the memory size for an exiting minikube cluster. Please first delete the cluster.
and

😿 Failed to start ssh bare metal machine. Running "minikube delete -p foo" may fix it: config: please provide an IP address

we should had sticked with first advice

drewpca(pts/0):~% minikube start -p foo --memory 6GB
😄  [foo] m

Helm documentation states the following:
-1) (k8s) metadata.name is restricted to a maximum length of 63 characters because of limitations to the DNS system
-2) For that reasons, release names are (DNS labels that are) limited to 53 characters

Statement 1) is not correct.
k8s does not impose a max length of 63 characters on resource names.
The actual max length for a resource name is 253 c

Beta release: Grayscale release can not select client IP needs to be filled in manually, hope to add support to select IP directly from the connected client
Beta发布: 灰度发布不能选择客户端ip 需要手动填写，希望增加支持从已连接的客户端直接选择ip

Describe the bug
When selecting "Help" -> "Documentation" Lens navigates to https://docs.k8slens.dev/ but should navigate to the documentation corresponding to the running version (e.g. https://docs.k8slens.dev/v4.1.0/).

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

In what area(s)?

/area test-and-release

Describe the proposal

Currently before each rc release

When I run "vtctlclient help ApplyRoutingRules", I get informations on how to use this option. But when I run "vtctlclient help GetRoutingRules", I do not get such informations, and it looks like the routing rules are displayed. Output below.

jgagne@ip-172-31-40-211:~/my-vitess-example$ vtctlclient help GetRoutingRules
{

}
jgagne@ip-172-31-40-211:~/my-vitess-example$ vtctlclient hel

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

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.

Hi,
i want to use the parameter --images=
in a skaffold shell command to hand over 2 images.
What is the exact syntax? I can get it only working for one...
Best regards
Stefan

skaffold deploy -p gke -i 'image1 image2' -t latest

does not work...

Just like there was an issue to make the jib.to.tags and jib.to.auth to be lazyly evaluated I would need to have the container.labels do the same. Even the reason is the same. I use com.gorylenko.gradle-git-properties Gradle plugin and would like to reuse its properties to add labels to my images. Something like that:

jib {
    container {
        labels = [
            'org.label-schema.

FEATURE REQUEST:
Hi,

I see that there is nothing in the kargo repo related to docker login stuff and more precisely nothing about the ability to make kubernetes pull images from private registries such as ECR.

I have a solution for this that currently works for ECR and CoreOS and that could be extended to different registries solutions (azure one, custom private registry on premi

/kind feature

This is a sub-issue from #5494.
We need to remove any f"strings" from the backend of the Jupyter web app in order to be able to use lower versions from Python 3.6 to run it.

/good-first-issue