Files
aptly-containerized/charts/aptly/Chart.yaml
T
f.weber a08ed898e8
CI / lint (push) Failing after 3s
CI / smoke-test (push) Failing after 5s
Release chart / release (release) Successful in 6s
Update Helm chart version and modify probes to use exec for readiness and liveness checks
2026-08-13 12:30:17 +02:00

37 lines
1.5 KiB
YAML

apiVersion: v2
name: aptly
description: >-
aptly (Debian repository management tool) on Kubernetes — a StatefulSet with
an nginx read/auth sidecar, a fully aptly-native values API, and declarative
repo/mirror/publish state reconciled via a Helm hook.
type: application
version: 0.2.1
appVersion: "1.6.3-1"
home: https://git.morlana.online/f.weber/aptly-containerized
sources:
- https://git.morlana.online/f.weber/aptly-containerized
- https://github.com/aptly-dev/aptly
keywords:
- aptly
- apt
- debian
- package-repository
- artifact-repository
maintainers:
- name: Florian Weber
email: f.weber@flweber.me
icon: https://www.aptly.info/img/logo.png
annotations:
artifacthub.io/license: MIT
artifacthub.io/links: |
- name: aptly upstream
url: https://www.aptly.info/
- name: Source
url: https://git.morlana.online/f.weber/aptly-containerized
artifacthub.io/signKey: |
fingerprint: FC35C0FAA26605C4C21C7BBFBF43884145E5AA94
url: https://git.morlana.online/f.weber/aptly-containerized/raw/branch/main/pubkeys/chart-signing.asc
artifacthub.io/changes: |
- kind: fixed
description: The aptly container's startup/readiness/liveness probes now exec curl against 127.0.0.1 instead of using httpGet. httpGet probes are dialed by kubelet against the pod IP, not localhost — since aptly listens on 127.0.0.1 only (by design, see proxy.enabled), that connection was always refused, leaving the pod stuck failing its startup probe forever despite aptly actually being healthy.