InfrayardReleases and roadmap
Available capabilities, versioned delivery and separately identified roadmap items.
Maintained by Solvia Lab s.r.o. · Updated
On this page
Choose Infrayard based on capabilities available in the release delivered to your organisation. Planned work is described separately below and is not a delivery commitment unless included in a written agreement.
Available capabilities#
- Create, scale, upgrade, access and destroy OKE clusters through the portal.
- Inspect Terraform execution logs and lifecycle status.
- Publish cluster templates and control role visibility.
- Configure global limits, per-user overrides and limit-increase requests.
- Protect cluster destruction with an admin review workflow.
- Use supported existing OCI compartments, VCNs and subnets.
- Download Kubernetes access files without requiring local OCI CLI setup in the default access workflow.
- Review cost estimates, Activity notifications and audit history.
- Sync available shapes and Kubernetes versions with compatibility filtering.
- Use customer-managed identity and a Helm-based customer installation.
Operational behaviour depends on cluster tier and network design; see requirements and cluster lifecycle.
Versioned delivery#
Customers receive released container images, pinned references, deployment values and applicable release guidance. Images can be pulled from the approved delivery registry or an agreed mirror. Source code and maintainer CI are not required for customer deployment.
Use the version and upgrade notes included with your supplied release. This public page does not assign invented release dates or release numbers to the current build. Track the exact image versions or digests running in your installation.
Planned work#
| Area | Direction |
|---|---|
| Gatekeeper AI | Optional assistance for cluster requests and Terraform failures, plus cost and policy insights; customer-controlled provider configuration |
| Cost and policy insights | Idle-cluster signals, anomaly alerts, right-sizing suggestions, drift and lifecycle risk visibility |
| Oracle database options | Optional Oracle-native database deployment backend alongside the existing PostgreSQL approach |
| In-cluster access agent | A future connectivity option for environments that cannot expose even a CIDR-restricted OKE API endpoint |
| Multicloud governance | Read-only inventory and governance for observed EKS, AKS and GKE clusters before lifecycle ownership |
| Non-OCI provisioning | Provider-specific lifecycle automation selected according to customer demand |
| OCI Marketplace | A future listing and guided deployment path |
These items can change in scope and order. Observing an external cluster does not imply Terraform state import or resource adoption. AI, multicloud and Marketplace capabilities are not included as available features solely because they appear here.
Request release information#
For the current supported release, compatibility notes or upgrade guidance for your installation, contact support@infrayard.eu. For product fit and upcoming requirements, request a demo.