Trinetra 5.5.3 release notes

Documentation baseline: 2026-09-15.

Highlights

Cloud resilience discovery, controlled validation, risk tracking, evidence, and history in one platform.
Versioned Kubernetes and Helm deployment path.
Installation-bound activation, periodic entitlement validation, expiry/grace handling, and enforced limits.
Explicit project and cluster enrolment with automatic first-use resource enrolment.
Read-only visibility remains available when licensed mutations are blocked.
Explicit filter application and stable page routing.
Google Cloud Marketplace Kubernetes BYOL distribution with a dedicated provider guide.
Marketplace parameter reference, immutable image-digest verification, customer-managed HTTPS ingress guidance, and explicit PVC backup/restoration procedures.
Separate directly contracted assisted-service option.

Available resource views and actions depend on the installed cloud integration.
Kubernetes mutation is restricted to the configured home cluster unless an integration explicitly supports another execution path.
Standalone virtual-machine discovery does not imply general automatic recovery.
Managed-database failover requires an eligible high-availability target, permissions, licensed capability, and an explicit safety gate.
Cloud audit sources can be eventually consistent.
Native compilation can raise the reverse-engineering barrier but does not guarantee prevention of all analysis.