Jintao Zhang

https://moelove.info/ [email protected]

@Kong Beijing, China @kubernetes Ingress-NGINX maintainer, @apache PMC member. Container, Docker, Go, Kubernetes, Python, Vim; he/him; Twitter: @zhangjintao9020

Results 618 comments of


Jintao Zhang

registry.k8s.io/ingress-nginx/controller:v1.10.0 has no s390x arch in the image manifest

Yes. We have not fix the problem during NGINX v1.25 build on s390x.

Allow configuring nginx worker reload behaviour, to prevent multiple concurrent worker reloads which can lead to high resource usage and OOMKill

/assign Thanks, I will take a look this week.

Allow configuring nginx worker reload behaviour, to prevent multiple concurrent worker reloads which can lead to high resource usage and OOMKill

Sorry for the long delay. Let me take a look

Allow configuring nginx worker reload behaviour, to prevent multiple concurrent worker reloads which can lead to high resource usage and OOMKill

Thank you for your contributions! I will finish the review this week. BTW this PR need rebase

Allow configuring nginx worker reload behaviour, to prevent multiple concurrent worker reloads which can lead to high resource usage and OOMKill

/retest

Allow configuring nginx worker reload behaviour, to prevent multiple concurrent worker reloads which can lead to high resource usage and OOMKill

/test pull-ingress-nginx-codegen

Allow configuring nginx worker reload behaviour, to prevent multiple concurrent worker reloads which can lead to high resource usage and OOMKill

I have created a PR https://github.com/kubernetes/ingress-nginx/pull/11344 It will unblock the failures of the codegen job.

Allow configuring nginx worker reload behaviour, to prevent multiple concurrent worker reloads which can lead to high resource usage and OOMKill

#11344 has been merged, let's do a rebase and the codegen will be passed

Mirror dockerhub kindest/node to a non rate limited registry

Although this may come as a surprise, I am able to offer a mirror of the China region if necessary. (Maybe this will make our migration easier. We can focus...

Mirror dockerhub kindest/node to a non rate limited registry

I prefer the second form, `registry.k8s.io/kind/node:v0.17.0-v1.26.1` * Not all registries can support multi-level nesting well * In the second form, we can think that one image contains multiple tags, right?