You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NGINX Ingress controller version:
Starting from 0.27.0 and up
Kubernetes version (use kubectl version):
Environment:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:
What happened:
Tried to upgrade my existing kustomize-based installation just by replacing the git tag for remote base. Ended up having quay.io/kubernetes-ingress-controller/nginx-ingress-controller:master in the manifests (as a workaround I patched it in my kustomization.yaml).
Checking the official documentation, it also features :master images (docs suggest to run kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.27.1/deploy/static/mandatory.yaml, which has :master tag).
What you expected to happen:
Having tagged commits reference an exact version, like it was in 0.26.2 and before.
What do you think went wrong? #4887 was merged and it affected all tags after that
NGINX Ingress controller version:
Starting from 0.27.0 and up
Kubernetes version (use
kubectl version
):Environment:
uname -a
):What happened:
Tried to upgrade my existing kustomize-based installation just by replacing the git tag for remote base. Ended up having
quay.io/kubernetes-ingress-controller/nginx-ingress-controller:master
in the manifests (as a workaround I patched it in mykustomization.yaml
).Checking the official documentation, it also features
:master
images (docs suggest to runkubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.27.1/deploy/static/mandatory.yaml
, which has:master
tag).What you expected to happen:
Having tagged commits reference an exact version, like it was in 0.26.2 and before.
What do you think went wrong?
#4887 was merged and it affected all tags after that
How to reproduce it:
Anything else we need to know:
/kind bug
The text was updated successfully, but these errors were encountered: