Feb 24, 2026 — App Platform v4.14.0
about 4 hours ago
This release introduces OpenTelemetry-based log collection as a replacement for Promtail, adds support for custom Kubernetes manifests in the values repository, and extends Kubernetes version support to v1.35. It also completes the removal of the Tempo tracing application, includes ArgoCD sync optimizations, and delivers a range of stability and bug fixes.
For a full list of changes, review the release notes on GitHub: Release v4.14.0.
New
- Added Kubernetes v1.35 support
- Replaced Promtail with an OpenTelemetry Collector for log collection, aligning the logging pipeline with the broader OpenTelemetry strategy already used for traces and metrics
- Added support for defining custom Kubernetes manifests directly in the values repository, giving platform users more flexibility to manage cluster resources alongside their application configuration
- Removed the Tempo distributed tracing application, completing its deprecation from the previous release
- Optimized Helm chart values generation for ArgoCD syncs, reducing the size of values passed during synchronization and improving sync performance
- Secrets can now be deployed as secretRef references in Helm chart values, improving security by avoiding plaintext secret values in chart configuration
- Run traces diagnostics command periodically (every 5 minutes for up to 30 minutes) to improve observability during troubleshooting
Changed
- Updated core applications. See the Core application changes table below for details.
Fixed
- Fixed an issue where password validity resets were not retried on all types of expiration errors in Keycloak
- Fixed buildpacks builds when using ORCS
- Fixed Harbor storage credentials not being correctly applied
- Fixed user arrays not being consistently sorted by name
- Fixed Harbor database backup object storage secret references
- Replaced kubectl calls with the Kubernetes client library for ArgoCD application management, improving reliability and reducing external dependencies
- Fixed team workloads not being effectively deleted when removed from configuration
- Fixed
serviceMonitorconfiguration in Loki values - Fixed ArgoCD projects rendering duplicate source repositories
- Fixed duplicate credentials warnings appearing in ArgoCD
Deprecated
- Minio
- Thanos
Removed
- Tempo
Core application changes
| App Name | Old Version | New Version | Notes |
|---|---|---|---|
| Alertmanager | 0.29.0 | 0.30.1 | Updated |
| Argo CD | 3.2.0 | 3.2.6 | Updated |
| Cert-manager | 1.19.1 | 1.19.2 | Updated |
| CloudNative PostgreSQL Operator | 1.27.1 | 1.28.0 | Updated |
| External DNS | 0.19.0 | 0.20.0 | Updated |
| Gitea | 1.24.7 | 1.25.4 | Updated |
| Grafana | 12.2.1 | 12.3.1 | Updated |
| Harbor | 2.14.0 | 2.14.2 | Updated |
| Ingress-NGINX | 1.14.0 | 1.14.2 | Updated |
| Istio | 1.27.3 | 1.28.3 | Updated |
| Keycloak | 26.4.2 | 26.5.1 | Updated |
| Minio | Deprecated | ||
| Tekton Pipelines | 1.3.1 | 1.6.0 | Updated |
| Loki | 2.9.15 | 3.6.4 | Updated |
| Prometheus | 3.7.3 | 3.9.1 | Updated |
| Sealed Secrets | 0.33.1 | 0.34.0 | Updated |
| Tempo | 2.6.0 | Removed | |
| Thanos | 0.36.1 | Deprecated |
Post-upgrade actions
Delete resources for Tempo
App Platform doesn’t automatically clean up all resources for apps that are removed and no longer supported (in case the user wants to keep using them). If you are no longer using Tempo and want to remove it and its resources, run the commands below:
kubectl delete application tempo-tempo -n argocd
kubectl delete namespace tempo