Your certificate (or certificates) for the names listed below will expire in 19 days (on 2025-06-17).
git.k-space.ee
*.minio-clusters.k-space.ee
longhorn.k-space.ee
playground-lauri.k-space.ee
> Your certificate (or certificates) for the names listed below will expire in 19 days (on 2025-06-17).
> git.k-space.ee
> *.minio-clusters.k-space.ee
> longhorn.k-space.ee
> playground-lauri.k-space.ee
Smells not OK, possibly regression of https://git.k-space.ee/k-space/kube/issues/36: https://git.k-space.ee/k-space/kube/commit/e632b90d2b499aaf4ee67072525ed50caf7329bd, https://git.k-space.ee/k-space/kube/commit/a280a19772eefb90a402baa7ebd170d536a81365
rasmus
added the upkeep label 2025-06-04 11:56:32 +00:00
Unsure if touching cert-manager and related resources did anything. Found out that gitea doesn't run through treafik at all. Debugging lead to 'everything works, but traefik isn't exchanging certs' (including for others, on wildcard-tls, which does run through traefik). End result was to restart gitea to pick up the new cert. Gitea pod was 1w old, so question for the past remains, why cert wasn't renewed.
longhorn.k-space.ee should be normal, and configured under wildcard-tls, but may be actually deprecated, otherwise there'd be a notification for *.k-space.ee instead.
Unsure if touching cert-manager and related resources did anything. Found out that gitea doesn't run through treafik at all. Debugging lead to 'everything works, but traefik isn't exchanging certs' (including for others, on wildcard-tls, which does run through traefik). End result was to restart gitea to pick up the new cert. Gitea pod was 1w old, so question for the past remains, why cert wasn't renewed.
longhorn.k-space.ee should be normal, and configured under wildcard-tls, but may be actually deprecated, otherwise there'd be a notification for `*.k-space.ee` instead.
AFAIK minio-clusters dashboard is to-be-axed, not bothering with it. As there isn't much action to be done here (besides integrating gitea under traefik, or restarting the statefulset on renewal). Expecting the issue to pop up again, or not… logs leave desires.
AFAIK minio-clusters dashboard is to-be-axed, not bothering with it. As there isn't much action to be done here (besides integrating gitea under traefik, or restarting the statefulset on renewal). Expecting the issue to pop up again, or not… logs leave desires.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Smells not OK, possibly regression of #36:
e632b90d2b,a280a19772Unsure if touching cert-manager and related resources did anything. Found out that gitea doesn't run through treafik at all. Debugging lead to 'everything works, but traefik isn't exchanging certs' (including for others, on wildcard-tls, which does run through traefik). End result was to restart gitea to pick up the new cert. Gitea pod was 1w old, so question for the past remains, why cert wasn't renewed.
longhorn.k-space.ee should be normal, and configured under wildcard-tls, but may be actually deprecated, otherwise there'd be a notification for
*.k-space.eeinstead.AFAIK minio-clusters dashboard is to-be-axed, not bothering with it. As there isn't much action to be done here (besides integrating gitea under traefik, or restarting the statefulset on renewal). Expecting the issue to pop up again, or not… logs leave desires.