Marco Ebert
Marco Ebert
First of all you seem to be using v1.2.0 of this Controller. This version is no longer supported for ages already. Additionally you seem to be running RKE. From a...
We already have NGINX v1.27.1 on `main` and since this project is using OpenResty, the best we can do is updating to OpenRest v1.27.1.2.
We are going to cut a v1.13 by end of June. I recently started doing monthly patch releases again and will try to cut a minor every 4 months or...
The latest release (v1.12.3) is not released from `main` branch. We start `release-*` branches for every minor release. New features and breaking changes are only getting merged to `main` and...
Yes, that's true, but v1.13.0 is not a _patch_ release.
I created https://github.com/kubernetes/ingress-nginx/pull/13524 to bring it to the latest OpenResty version. With the next minor end of June this will get published.
First of all we are not directly using NGINX, but OpenResty and manually compile everything. Second we stick to whatever versions OpenResty uses in their releases and also do an...
It's not as easy as that because `registry.k8s.io` is not just a single host, but a mirror and we usually first push container images to a [region specific staging registry](https://github.com/kubernetes/ingress-nginx/blob/main/images/Makefile#L19)...
Ok, I took a quick look, should be doable. But no promises.
It does work, probably. But it's not as straightforward as it might look like. There is no direct push to `registry.k8s.io`. In fact artifacts get pushed to a staging registry...