Skip to main content

EVA Agent Helm Chart Release Notes

Version 2.7.0​

Added​

  • release/2.7.0/eva-agent/values.yaml, values-aws.yaml, values-k3s.yaml, values-ncp.yaml - Added the 2.7.0 release template set for EVA Agent.
  • eva-agent/templates/service.yaml - Added support for configurable service.portName and fixed HTTP service.nodePort.
  • release/2.7.0/eva-agent-vllm/values*.yaml - Added explicit router/engine service exposure fields for routerSpec.serviceType, routerSpec.nodePort, servingEngineSpec.modelSpec[].serviceType, and servingEngineSpec.modelSpec[].nodePort.
  • eva-agent-vllm/templates/service-router.yaml, service-vllm.yaml - Added fixed HTTP nodePort support for router and per-engine services.
  • eva-agent-vllm/templates/extra-objects.yaml, scaledobject-vllm.yaml and additional tests - Added upstream-aligned templates/tests that are now present in the downstream 0.1.10 package.

Changed​

  • eva-agent/Chart.yaml - version / appVersion changed from 2.6.0 to 2.7.0.
  • release/2.7.0/eva-agent/values.yaml - image.tag changed from 2.6.0 to 2.7.0.
  • release/2.7.0/eva-agent/values.yaml - Added default LOGURU_LEVEL=INFO to the chart environment values.
  • eva-agent-vllm/Chart.yaml - Downstream chart version changed from 0.1.8 to 0.1.10.
  • eva-agent-vllm/README.md - Replaced the older bundled values reference with fork-specific guidance pointing to the upstream vllm-stack 0.1.10 documentation.
  • eva-agent-vllm router/engine service templates - Updated service labeling and exposure controls so HTTP services can be rendered as ClusterIP, NodePort, or LoadBalancer with explicit HTTP node ports.

Removed​

  • No packaged chart templates were removed in this release note scope.

Notes​

  • eva-agent-vllm fixed nodePort settings apply to the primary HTTP service port only; auxiliary ports such as router 9000 and engine 55555/9999 remain auto-assigned unless patched separately.
  • The downstream eva-agent-vllm 0.1.10 package is intended to stay aligned with upstream vllm-stack 0.1.10 while preserving EVA-specific storage and service exposure behavior.

Version 2.5.0​

Added​

  • release/2.5.0/eva-agent/values-ncp.yaml - Added NCP-only override including sharedPvcStorage.mode: dynamic
    • Sets the PV provisioning mode (static/dynamic)
    • K3s environments operate with static + NFS settings
    • Cloud environments operate with dynamic
  • release/2.5.0/eva-agent-vllm/values-ncp.yaml - Added NCP-only override including routerSpec.staticBackends, routerSpec.staticModels, routerSpec.nodeSelectorTerms, servingEngineSpec.modelSpec[].name, servingEngineSpec.modelSpec[].modelURL, servingEngineSpec.modelSpec[].repository, servingEngineSpec.modelSpec[].tag, servingEngineSpec.modelSpec[].nodeSelectorTerms
  • release/2.5.0/eva-agent-qdrant/values.yaml - Added snapshotPersistence.enabled, snapshotPersistence.accessModes[], snapshotPersistence.size, snapshotPersistence.snapshotsVolumeName, snapshotPersistence.storageClassName
    • Previously, Qdrant DB backup files (snapshot) were not stored on a persistent volume
    • Qdrant DB backups are now stored persistently by default
  • release/2.5.0/eva-agent-qdrant/values.yaml - Added snapshotRestoration.enabled, snapshotRestoration.pvcName, snapshotRestoration.mountPath, snapshotRestoration.snapshots[]
    • Values for recovery from external snapshot files
    • Uncomment and fill in actual values when recovery from an external snapshot is required
  • release/2.5.0/eva-agent-qdrant/values-ncp.yaml - Added NCP-only override value including nodeSelector

Changed​

  • Chart.yaml.version, Chart.yaml.appVersion - Changed from 2.4.0 to 2.5.0
  • release/2.5.0/eva-agent/values.yaml - image.tag changed from 2.4.3 to 2.5.0
  • release/2.5.0/eva-agent/values.yaml - persistence.s3Sync.enabled changed from false to true
  • The public schema for persistence.s3Sync has been reduced.
  • release/2.5.0/eva-agent-vllm/values-ncp.yaml - Baseline values for routerSpec.staticBackends, routerSpec.staticModels, servingEngineSpec.modelSpec[].tag, servingEngineSpec.modelSpec[].initContainer.command[] were set

Removed​

  • values.yaml, lint-values.yaml - Removed persistence.s3Sync.image, persistence.s3Sync.source, persistence.s3Sync.destination, persistence.s3Sync.extraArgs

Notes​

  • If you update to use the Qdrant snapshot volume, helm uninstall and reinstall are required
    • Data is not deleted even if you install again with helm install