Version mismatch of falco-operator container tag

[nestorsalceda]

In DockerHub, there is a falco-operator image which has the 0.12.1 tag. But in the Makefile and in the deployment manifests the tag value is v0.12.1.

AFAIK, the convention followed for Falco is to use vX.XX.X for git tag name and use just X.XX.X for images uploaded to DockerHub.

So I think, this should be fixed because otherwise an ErrImagePull is received.

Thanks!

[mumoshu]

@nestorsalceda Thanks!

I'm going to fix this, but how should I push the resulting image to the dockerhub "falcosecurity" org?

Would you mind inviting me (@mumoshu in dockerhub as well) to the dockerhub org, or "falco-operator" docker repo under the org, so that I can probably push it myself?

[acim]

You should either tag your Docker images with prefix v or just keep tagging as you do and remove v from the Helm chart values. I will PR with the second solution today.

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale