Image versioning?

[jperville]

Would it be possible to publish official releases of this project (applying to code and also to the docker image at https://hub.docker.com/r/tnozicka/openshift-acme), so that I can deploy your project without worrying about incompatible changes to environment variables, cluster roles etc?

I ask because I deployed your project many times in the past 8 months without any problems (after patching the openshift router to support updating the let's encrypt certificate when the route is secured with redirect insecure edge termination policy); on my latest deployment the acme controller fails to boot because of missing OPENSHIFT_ACME_EXPOSER_IP environment variable. I checked and since the cluster role has also changed I now have to retest my deployment to be compatible with the new image.

[twhiston]

big +1 on this as well, we had to turn off image updates for this project as the changes sometimes broke things in production for us, it would be great to have versioned images we could pin to

[cchaudier]

👍 And if we can have also a releases tag to have a point in time. I want tu use this on production for one of my customers.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

[hypery2k]

any update on this?

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.