example sigsci-values.yaml causes controller pods to fail with ImagePullBackoff

[Schnitzel]

When applying the sigsci-values.yaml from the documentation to the ingress-nginx helm chart, the ingress-nginx pods fail to start with:

Failed to pull image "signalsciences/sigsci-nginx-ingress-controller:0.48.1@sha256:e9fb216ace49dfa4a5983b183067e97496e7a8b307d2093f4278cd550c303899": rpc error: code = Unknown desc = Error response from daemon: manifest for signalsciences/sigsci-nginx-ingress-controller@sha256:e9fb216ace49dfa4a5983b183067e97496e7a8b307d2093f4278cd550c303899 not found: manifest unknown: manifest unknown

The reason for this is that the digest that is provided via the original helmchart:
https://github.com/kubernetes/ingress-nginx/blob/05a3d144de71933a43d49fd2ea38ef06e76bdaca/charts/ingress-nginx/values.yaml#L19

does not match the digest of the sigsci-nginx-ingress-controller images, there are two ways to fix it:

1. check the dockerhub https://hub.docker.com/r/signalsciences/sigsci-nginx-ingress-controller/tags?page=1&ordering=last_updated for the correct digest and define it as controller.image.digest
2. set controller.image.digest to false which then it will be ignored and not used, see https://github.com/kubernetes/ingress-nginx/blob/05a3d144de71933a43d49fd2ea38ef06e76bdaca/charts/ingress-nginx/templates/controller-deployment.yaml#L75

[SA-Egress]

Faced the same issue. Spent far too long wondering why it wasn't working.