For release v0.4.0, the deployment.yaml file attached to the release page contains a reference to a docker image called synadia/nats-streaming-operator:v0.4.0, which does not exist. Rather, an image called synadia/nats-streaming-operator:0.4.0 exists (the v is missing).
Also, the deployment.yaml file located in the repository at the commit which is tagged v0.4.0 contains a reference to a docker image synadia/nats-streaming-operator:v0.3.0-v1alpha1.
You could sort this out by updating the deploy directory before cutting a release, and releasing a v0.4.1 or 0.4.1 release on both github and docker hub once it's consistent.
For release
v0.4.0
, thedeployment.yaml
file attached to the release page contains a reference to a docker image calledsynadia/nats-streaming-operator:v0.4.0
, which does not exist. Rather, an image calledsynadia/nats-streaming-operator:0.4.0
exists (the v is missing).Also, the deployment.yaml file located in the repository at the commit which is tagged
v0.4.0
contains a reference to a docker imagesynadia/nats-streaming-operator:v0.3.0-v1alpha1
.You could sort this out by updating the deploy directory before cutting a release, and releasing a v0.4.1 or 0.4.1 release on both github and docker hub once it's consistent.