search

tnozicka / openshift-acme

ACME Controller for OpenShift and Kubernetes Cluster. (Supports e.g. Let's Encrypt)
Apache License 2.0
319 stars 116 forks source link

[Information Request] docker image update policy #137

Closed maorfr closed 3 years ago

maorfr commented 4 years ago

Hello and thank you for all the amazing work!

We would like to understand the policy behind updating images in quay.io/tnozicka/openshift-acme.

When are images pushed and updated?

Thank you very much again!

openshift-bot commented 4 years ago

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

maorfr commented 4 years ago

/remove-lifecycle stale

tnozicka commented 4 years ago

Hi @maorfr,

thanks and sorry this slipped out of my radar. I've updated the issue template a while back to automatically cc me.

The images are built from master and pushed to registry.svc.ci.openshift.org/openshift-acme/0.9 (tags controller, exposer) right after a merge to master happens. https://github.com/openshift/release/blob/02ba446/ci-operator/config/tnozicka/openshift-acme/tnozicka-openshift-acme-master.yaml It is being mirrored to quay.io in about an hour it think by this spec https://github.com/openshift/release/blob/02ba446e097581806a3ec25345ede712486afc8a/core-services/image-mirroring/tnozicka/mapping_tnozicka_openshift-acme

maorfr commented 4 years ago

thanks a lot @tnozicka!

cc @rporres

rporres commented 4 years ago

Hi @tnozicka. Could you explain the reason behind not having versioned tags? You're only keeping a sort of latest and 0.9 tags for exposer and controller components...

openshift-bot commented 3 years ago

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

Alveel commented 3 years ago

Gentle poke @tnozicka, also interested.

Alveel commented 3 years ago

/remove-lifecycle stale

openshift-bot commented 3 years ago

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

rporres commented 3 years ago

/remove-lifecycle stale

openshift-bot commented 3 years ago

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 commented 3 years ago

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[bot] commented 3 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/tnozicka/openshift-acme/issues/137#issuecomment-883416668): >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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.