This major release adds full Kubernetes Gateway API support. In addition, Tekton is now an optional application so that the platform can be deployed without CI/CD pipeline components. It also includes installation and upgrade protocol enhancements.

📘

For a full list of changes, review the release notes on GitHub: Release v5.0.0.

New

• Native Gateway API routing for all services in the platform
• Tekton is now optional, allowing users to deploy the platform without CI/CD pipeline components
• The otomi.git.username property is now optional
• The tini binary is used as the operator init process to eliminate zombie git processes
• OAuth2 proxy now passes the Accept header, improving compatibility with API clients
• Harbor registry now requests more memory and CPU resources by default
• Improvements to upgrade procedures
• Improvements to installation procedures

Changed

• [Breaking change] Support for Ingress-NGINX has been discontinued in this release. Istio Gateway is the replacement. See Upgrade Notes.
• [Breaking change] TLS passthrough functionality has been eliminated; all TLS endpoints are now terminated by the Istio Gateway.
• Updated core applications. See the Core application changes table below for details.

Fixed

• Core apps now always use the desired storage class on Linode
• Auto sync is now always correctly enabled in ArgoCD
• Removed Gitea access to the API, which tightens security
• App files are now cleaned upon deletion migration, preventing stale resources
• Manifest folder is always created after the platform upgrade

Core application changes

Upgrade notes

When upgrading App Platform to v5.0.0, Ingress CR is automatically migrated to Gateway API CRs for both the platform and team services. This process generally takes a few minutes, during which there is a brief service interruption. Please plan accordingly.