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
The image for the default-backend defaults to k8s.gcr.io/defaultbackend-amd64 in the helm chart, which naturally fails when deploying on arm64. It would be nice to have it point to a manifest with all supported architectures (at least amd64/arm64)
The text was updated successfully, but these errors were encountered:
Thanks I'll have a look on the options out there. In the mean time you can try simply not to enable the default backend, haproxy ingress will make haproxy to expose a simple 404 page itself if the default backend isn't configured. Other than that since v0.14 you can also create your own 404 page, maybe you want to give this a try.
Thanks @jcmoraisjr, disabling the default-backend didn't work out for me at first glance anyway (something with not getting any certs from cert-manager). I'll just keep it on x86_64 for now...
The image for the default-backend defaults to
k8s.gcr.io/defaultbackend-amd64
in the helm chart, which naturally fails when deploying on arm64. It would be nice to have it point to a manifest with all supported architectures (at least amd64/arm64)The text was updated successfully, but these errors were encountered: