[Bug]: Unable to pull image - icinga/icinga-kuberbetes:0.4.0

[ak2766]

Affected Chart

icinga-stack

Which version of the app contains the bug?

0.7.0

Please describe your problem

I'm trying to evaluate icinga in kubernetes but I'm hitting this road block:

  Warning  Failed     3m1s (x5 over 6m24s)  kubelet            Failed to pull image "icinga/icinga-kubernetes:0.4.0": rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/icinga/icinga-kubernetes:0.4.0": failed to resolve reference "docker.io/icinga/icinga-kubernetes:0.4.0": docker.io/icinga/icinga-kubernetes:0.4.0: not found
  Warning  Failed     3m1s (x5 over 6m24s)  kubelet            Error: ErrImagePull
  Warning  Failed     78s (x19 over 6m24s)  kubelet            Error: ImagePullBackOff
  Normal   BackOff    55s (x21 over 6m24s)  kubelet            Back-off pulling image "icinga/icinga-kubernetes:0.4.0"

I've validated that I'm running the latest available helm chart:

$ > helm search repo icinga/icinga-stack --versions | head
NAME               	CHART VERSION	APP VERSION	DESCRIPTION                                       
icinga/icinga-stack	0.7.0        	0.7.0      	Icinga is a monitoring system which checks the ...
icinga/icinga-stack	0.6.0        	0.6.0      	Icinga is a monitoring system which checks the ...
icinga/icinga-stack	0.5.1        	0.5.1      	Icinga is a monitoring system which checks the ...
icinga/icinga-stack	0.5.0        	0.5.0      	Icinga is a monitoring system which checks the ...
icinga/icinga-stack	0.4.0        	0.4.0      	Icinga is a monitoring system which checks the ...
icinga/icinga-stack	0.3.0        	0.3.0      	Icinga is a monitoring system which checks the ...
icinga/icinga-stack	0.2.0        	0.2.0      	Icinga is a monitoring system which checks the ...
icinga/icinga-stack	0.1.0        	0.1.0      	Icinga is a monitoring system which checks the ...

Help!

[ak2766]

Looks like this has already been reported: #80

Changing tag from 0.4.0 to latest for icinga/icinga-kubernetes image allowed the deployment to successfully deploy.

This was of course done blindly and the side effects could be what's reported in the issue linked to above.