Htv3.7.1 -

apiVersion: apps/v1
kind: Deployment
metadata:
  name: htv-ingress
spec:
  replicas: 3
  selector:
    matchLabels:
      app: htv-engine
  template:
    metadata:
      labels:
        app: htv-engine
        version: "3.7.1"
    spec:
      containers:
      - name: htv
        image: htv/engine:3.7.1
        ports:
        - containerPort: 8080
        env:
        - name: HTV_CONFIG_MODE
          value: "kubernetes"
        readinessProbe:
          httpGet:
            path: /healthz
            port: 8080

The native support for Prometheus metrics (exposed at /metrics) makes HTV3.7.1 a first-class citizen in observability ecosystems.

htv3.7.1 reads like a careful craftsperson rather than a headline-hungry showrunner: htv3.7.1

Cause: The service name changed in some distributions from htvd to htv3.7.1.
Solution: Enable the new service: The native support for Prometheus metrics (exposed at

systemctl disable htvd
systemctl enable htv3.7.1
systemctl start htv3.7.1

The HTV roadmap indicates that version 3.8 is slated for Q4 of this year, with experimental features like WebAssembly (WASM) plugins and a distributed lock manager. However, HTV3.7.1 will remain a Long-Term Support (LTS) candidate due to its stability profile. The LTS tag means security backports will continue for at least 24 months. The HTV roadmap indicates that version 3

If your organization prioritizes reliability over new features, HTV3.7.1 is the version to standardize on.

For air-gapped or highly secure environments: