-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rke2 ingress upgrade fails 1.31.4 -> 1.31.5 #7652
Comments
Please show the value of your rke2-ingress-nginx HelmChartConfig valuesContent. It looks like something in there is clobbering the top-level global:
image:
# -- Registry host to pull images from.
registry: registry.k8s.io
systemDefaultRegistry: ""
systemDefaultIngressClass: "" It must either not exist in your values, or also be a map. |
it seems that however, it happens also if I use also only bundled values and enable defaultBackend:
these are my values (public address and dns name hidden)
|
Ah. I suspect that the template scope for the defaultBackend image helper was broken by the most recent chart update - cc @dereknola. We should probably have a test that covers the defaultBackend, I don't think it sees MUCH use since generally all it did for most folks was send a static 404 page. In the mean time you might try this: defaultBackend:
enabled: true
autoscaling:
enabled: false
image:
repository: cerit.io/cerit/default-backend
tag: "v1.1"
readOnlyRootFilesystem: false
global:
systemDefaultRegistry: "" |
our use case is that it sends better page than just pure 404 and it handles also 500 and 503 error pages explaining what happened and how it can be fixed.
did not help. It seems, that for some reason, even such fix in |
Yeah, the root scope (
This should do it until we can fix the chart in the February release: defaultBackend:
enabled: true
autoscaling:
enabled: false
image:
repository: cerit.io/cerit/default-backend
tag: "v1.1"
readOnlyRootFilesystem: false
Values:
global:
systemDefaultRegistry: ""
defaultBackend:
image:
repository: cerit.io/cerit/default-backend
tag: "v1.1" |
yes, this workaround does work. |
Environmental Info:
RKE2 Version: v1.31.5+rke2r1
Node(s) CPU architecture, OS, and Version: Linux kub-h1.priv.cerit-sc.cz 6.8.0-50-generic #51-Ubuntu SMP PREEMPT_DYNAMIC Sat Nov 9 17:58:29 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration: 6 servers
Describe the bug:
helm pod with ingress upgrade gets error:
if
defaultBackend
is enabled via values:Steps To Reproduce:
download the chart: rke2-ingress-nginx-4.12.003.tgz. untar, change
defaultBackend
totrue
in budled values, and runhelm template test . -f values.yaml
.Expected behavior:
upgrade ingress controller
Actual behavior:
error
The text was updated successfully, but these errors were encountered: