Dmitry Fedorov

We use ubuntu in our project stack, because alpine with glibc/musl has weird issues in the recent past with stuff like networking, sporadic performance drops and segfaults

and there is more pleasure if it has build from latest source, like 1.17.9, because, for example it has > *) Bugfix: socket leak when using HTTP/2.

same problem > INFO[0030] RUN apt-get update && apt-get -y install wget build-essential git libpcre3 libpcre3-dev zlib1g zlib1g-dev libssl-dev INFO[0030] Found cached layer, extracting to filesystem error building image: error...

my docker image ``` FROM nginx:1.17.8 COPY devops/nginx/ssl/certbundle.pem /etc/ssl/certbundle.pem COPY devops/nginx/ssl/1.key /etc/ssl/1.key COPY devops/nginx/nginx.conf /etc/nginx/nginx.conf COPY devops/nginx/default.conf /etc/nginx/conf.d/default.conf RUN apt-get update && apt-get -y install wget build-essential git libpcre3 libpcre3-dev...

> Apologies if I'm misunderstanding you; my suggestion was to clear the cache when going from a known bad version of kaniko to a good version > > E.G >...

may be its envoy timeout?

Hi, thank for this feature, but I have a question, in kafka we have migration for partition if our instance of counsumer gone down, but in this case are there...

@jnmoyne I understand your point of view, but if I have 3 instance I want to balance my work and have 1 consumer per 1 instance of my service, but...

If I have one subscriber/worker per partition and my instance go down, and there is no more free resources in my cluster, work will stop. Moreover for example in k8s...

That's true, but in real life there are many different situations (some about resources i said) and changing consumers on the fly is good feature. We will try to make...